Closed
Bug 277099
Opened 20 years ago
Closed 20 years ago
columnar layout in roc's blog renders badly in trunk [columns]
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: yusufg, Unassigned)
References
()
Details
Attachments
(1 file)
|
3.32 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050104 Firefox/1.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050104 Firefox/1.0+ Hi, Visiting roc's blog in Firefox 1.0+ nightly I see the blog rendered in a columnar fashion whereas visiting the url with Firefox 1.0, the blog renders as intended aebrahim on irc confirmed the same bad rendering with a Windows nightly build He was using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050101 Firefox/1.0+. He sees the blog rendering in 4 columns at 1600x1200 whereas I see the blog rendering as 3 columns at 1024x768 Reproducible: Always Steps to Reproduce: 1.Visit http://weblogs.mozillazine.org/roc/ with Firefox nightly 2. Observe the rendering 3.Visit above url with Firefox 1.0 4. Observe the rendering Actual Results: Rendering is columnar in nightly build Expected Results: Rendering in nightly build should be same as Firefox 1.0
Comment 1•20 years ago
|
||
Looks a bit strange in Mozilla/5.0 (X11; U; Linux i686; nb-NO; rv:1.8a6) Gecko/20050103 as well. Moving to layout.
Assignee: firefox → nobody
Component: General → Layout
Product: Firefox → Core
QA Contact: firefox.general → core.layout
Version: unspecified → Trunk
| Reporter | ||
Comment 2•20 years ago
|
||
moving to core/layout and asking for blocking 1.8a6
Flags: blocking1.8a6?
Comment 3•20 years ago
|
||
err, isn't this blog _supposed_ to render in columns, and ff 1.0 just does not support that?
Comment 4•20 years ago
|
||
Yes, it is. I didn't say it shouldn't, I said it looked strange :) I guess I should've read the initial description, I just commented from request on IRC "if the site looked strange in your build or not". The specific problem I saw was the image <http://weblogs.mozillazine.org/roc/archives/BOI.jpg>, which overflows 60-70% to the right.
| Reporter | ||
Comment 5•20 years ago
|
||
changing summary and specifically mentioning "columns" as requested by roc in https://bugzilla.mozilla.org/show_bug.cgi?id=251162#c54
Summary: roc's blog renders well in Firefox 1.0 but badly in Firefox 1.0+ nightly → columnar layout in roc's blog renders badly in trunk [columns]
Comment 6•20 years ago
|
||
(In reply to comment #4) > The specific problem I saw was the image > <http://weblogs.mozillazine.org/roc/archives/BOI.jpg>, which overflows 60-70% to > the right. It overflows without columns also, if the viewport is narrower than ~800 pixels. What seems more serious is that if you move the image to the beginning of the <div class="columns">, text in subsequent columns is rendered on top of the image, as in this testcase.
Comment 7•20 years ago
|
||
I just tested this in <http://archive.mozilla.org/pub/mozilla/nightly/2004-10-30-07-trunk/>, and it behaves - as far as I could see - just like todays build. So it isn't an regression, at least.
Comment 8•20 years ago
|
||
The behavior described in comment 4 and comment 6 is correct given the markup on that page. So what exactly is this bug about, if I may ask?
Comment 9•20 years ago
|
||
I did find one issue with that page, which I've filed, with minimal-ish testcase, as bug 277355.
Comment 10•20 years ago
|
||
(In reply to comment #8) > The behavior described in comment 4 and comment 6 is correct given the markup on > that page. Which behaviour described in comment 6 is correct? If you mean > It overflows without columns also, if the viewport is narrower than ~800 > pixels. then that's what I was saying myself. If you mean the next part > if you move the image to the beginning of the > <div class="columns">, text in subsequent columns is rendered on top of the > image then I'm very surprised to discover that that is correct behaviour. Can you explain?
Comment 11•20 years ago
|
||
I mean both parts of the behavior. The image is overflowing its parent, but the overflowing parts should still be rendered. The overflow setting on the image, which I presume was meant to prevent this, is irrelevant here, since that applies to the _children_ of the image (none in this case). There don't seem to be any provisions for clipping overflow in columns or otherwise handling it in the spec, but that's something to bring up with the working group...
Updated•20 years ago
|
Flags: blocking1.8a6? → blocking1.8a6-
What bz said.
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
•