Closed Bug 471421 Opened 12 years ago Closed 10 years ago
Page layout broken
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081229 Shiretoko/3.1b3pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081229 Shiretoko/3.1b3pre The page http://www.boston.com/sports/football/patriots/articles/2008/12/29/not_enough____but_they_gave_plenty/ is laid out incorrectly. The page is correctly (sufficiently good) laid out using Google Chrome. The incorrect behavior was observed in both safe and unsafe modes. Reproducible: Always Steps to Reproduce: 1.Select http://www.boston.com/sports/football/patriots/articles/2008/12/29/not_enough____but_they_gave_plenty/ Actual Results: The page is laid out incorrectly. Video overlays and obscures text. Text is center justified. Among others. Expected Results: A layout more like what Google Chrome currently produces.
Confirmed with latest trunk on Windows XP.
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → Trunk
It regressed in two steps. The first one is a very long regression range: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-09-30+07%3A00%3A00&enddate=2008-10-01+06%3A00%3A00 The second range is http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-10-03+03%3A00%3A00&enddate=2008-10-04+07%3A00%3A00 and this can only be Bug 458440. So the first one is probably Bug 364315.
(In reply to comment #2) > and this can only be Bug 458440. So the first one is probably Bug 364315. Oh well, not sure :/
No longer blocks: 364315
It's not retrievable what exactly has broken it. It started during the first range (page became partially white), and on 3 Oct 2008 the page changed rapidly at least 3 times while only two bugs are mentioned in the mozilla central list of this day so at least both bugs have caused a change.
The site has fixed itself.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.