Closed
Bug 270175
Opened 20 years ago
Closed 17 years ago
Page view is wrong (-moz-float-edge)
Categories
(Core :: Layout: Floats, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: karexx, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
376 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041115
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041115
It the page http://geekygurl.blogspot.com/ (which was created from a default
blogspot template) the stuff (links, etc) that should be appearing in the larft
margin, get thrown down at the bottom. This is in the latest Mozilla as well as
in the latest Firefox on my PC. This does not happen in any other browser (PC or
Mac).
Reproducible: Always
Steps to Reproduce:
1. Go to http://geekygurl.blogspot.com/
2. Look at the bottom of the page
3. That stuff should be in the left margin and IS in the left margin using all
other browsers on both Mac and PCs (Explorer, Safari, AOL)
Expected Results:
The links and stuff at the bottom of the page should be in the left frame.
Comment 1•20 years ago
|
||
The page doesn't even use frames, so how can it be a frames problem?
->Layout
Component: Layout: HTML Frames → Layout
Keywords: qawanted
QA Contact: core.layout.html-frames → core.layout
Comment 2•20 years ago
|
||
Looks the same in opera and moz. In konqueror it displays as intended though.
Comment 3•20 years ago
|
||
The centered <ul> is pushed below the right-floated div. in IE it isn't. Note
the usage of align="center".
Comment 4•20 years ago
|
||
Possibly valid(?), CC'ing bzbarsky.
Comment 5•20 years ago
|
||
Does setting "-moz-float-edge: content-box" on the <li>s fix this?
Comment 6•20 years ago
|
||
Yes, setting style="-moz-float-edge: content-box;" on the <LI>s does fix it.
Updated•20 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Page view is wrong → Page view is wrong (-moz-float-edge)
Fixed by the reflow branch landing (bug 300030). If it hadn't been, it probably would have been fixed by the checkin of bug 413840 today.
Updated•17 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•