Closed
Bug 155255
Opened 23 years ago
Closed 23 years ago
Absolute left position effected by padding-left when position set by right
Categories
(Core :: Layout, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: ssrit, Assigned: attinasi)
References
()
Details
(Keywords: testcase)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020612
BuildID: 2002061223
That's a bit hard to explain. I have an div position absolute, top 0, right 0.
It's in the top right corner of the document. Extending the padding-left
should leave the div in the upper right corner, however, the right border of the
div moves away from the right border of the window while at the same time
extending the left padding correctly.
My document is a correctly formed XML document marked with a correct XHTML 1.1
doctype. IE does view this as expected (drat!)
Reproducible: Always
Steps to Reproduce:
div {
border: 1px solid #000;
position: absolute;
top: 0px;
right: 0px;
padding-left: 50px;
}
I just tried to write a testcase for this and it worked as I expected. Could
you attach a testcase that shows the problem?
| Reporter | ||
Comment 2•23 years ago
|
||
Put this together: http://www.drwilco.net/~ssrit/mozbug.htm
Updated•23 years ago
|
QA Contact: petersen → amar
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Could you test a current trunk build?
| Reporter | ||
Comment 4•23 years ago
|
||
Im not sure what you mean by trunk... im a bit new at this mozilla bugzilla.
However, I downlaoded 1.1a alpha for linux x86 and the problem still exists.
That is 2002062601.
| Reporter | ||
Comment 6•23 years ago
|
||
2002061108 has the same problem as well. Im not 100% clear on which version all
these numbers coorespond to anymore.
Updated•23 years ago
|
Target Milestone: --- → Future
Comment 8•23 years ago
|
||
-> WORKSFORME
2002-08-17-05 trunk Linux.
2002-08-18-08 trunk Windows 2000.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•