Closed
Bug 279340
Opened 20 years ago
Closed 20 years ago
text-align: right aligns absolutely positioned, inline elements
Categories
(Core :: Layout: Positioned, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: shadow2531, Unassigned)
References
()
Details
(Keywords: testcase)
User-Agent: Opera/8.00 (Windows NT 5.1; U; en) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 At http://home.tbbs.net/shadow/html/testcases/theserverside.com/spantest3.html , Gecko aligns the absolutely positioned spans to the right. This looks like a spec violation. The testcase is a representation of the current problem at www. theserverside.com. Firefox displays the page as the author wants it to, but Opera does not. It appears Opera is following the spec and Firefox is not. More info: http://forums.mozillazine.org/viewtopic.php?t=205000&highlight= http://my.opera.com/forums/showthread.php?s=&threadid=78932 Reproducible: Always Expected Results: I believe the page should have been displayed like Opera 8 beta 1 does. Confirm?
Updated•20 years ago
|
Updated•20 years ago
|
Severity: normal → minor
Component: Layout: Block and Inline → Layout: R & A Pos
OS: Windows XP → All
QA Contact: layout.block-and-inline → layout.r-and-a-pos
Comment 1•20 years ago
|
||
Mozilla's layout is correct, Opera is wrong. For 'position:absolute' boxes with 'auto' top/left/right/bottom the position should be the "static position". http://www.w3.org/TR/CSS21/visudet.html#abs-non-replaced-width One could argue that the static position should be slightly more to the left in Mozilla since that's where the element would be had it been normal flow, but that would require a full reflow of the element in normal flow and we don't do that and are not required to either since the spec says: "But rather than actually calculating the dimensions of that hypothetical box, user agents are free to make a guess at its probable position." -> INVALID
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•