Closed
Bug 356786
Opened 18 years ago
Closed 17 years ago
CSS Attribute FLOAT Acting Weird Randomly On First Load, or a SHIFT+Reload
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: adam, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061015 Minefield/3.0a1
If you visit the following test page, you'll see that some text information and a table done with CSS and DIV objects that use the attribute FLOAT to line up next to one another.
http://www.lostadam.net/trainer/test.html
On first page load, it sometimes won't break the alignment of the table rows. However, if you do a SHIFT+Refresh, you'll see that the row alignment breaks. If you hit refresh again, the page loads fine.
It doesn't do it every time and when it does break it's not always the same rows. There is a weird randomness to it, and combined with the fact that it doesn't do this on any other browser (not even Mac Firefox as far as I know), I believe this is a bug.
Reproducible: Sometimes
Steps to Reproduce:
1. Load that URL (http://www.lostadam.net/trainer/test.html)
2. Hit SHIFT+Refresh to load it again
3. If it doesn't break, hit SHIFT+Refresh again until it happens. It will happen eventually.
Actual Results:
The rows of DIV objects do not line up properly on every row every time the page loads.
Expected Results:
Every row of DIV objects should line up the same way every time.
The CSS and XHTML are both valid. The page is totally self contained with no external dependencies such as JS includes or graphics. It's been tested and seen to fail on "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7" and "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061015 Minefield/3.0a1"
I hope this is enough information. It is a frustrating problem that comes up in many of my designs lately.
Reporter | ||
Updated•18 years ago
|
Summary: CSS Attribute FLOAT Acting Weird Randomly On First Load, of a SHIFT+Refresh → CSS Attribute FLOAT Acting Weird Randomly On First Load, or a SHIFT+Refresh
Reporter | ||
Updated•18 years ago
|
Summary: CSS Attribute FLOAT Acting Weird Randomly On First Load, or a SHIFT+Refresh → CSS Attribute FLOAT Acting Weird Randomly On First Load, or a SHIFT+Reload
Reporter | ||
Comment 1•18 years ago
|
||
After additional testing, this seems to be happening on both the Mac version of Firefox, and linux versions.
Reporter | ||
Updated•18 years ago
|
OS: Windows XP → All
Hardware: PC → All
Comment 2•18 years ago
|
||
I can get the problem to happen if I "shift-reload" a few times on the given testcase. Please excuse my next to none knowledge of CSS.
"Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061104 Minefield/3.0a1"
Comment 3•17 years ago
|
||
Reporter, do you still see this problem with the latest trunk build? If not, can you please close this bug as WORKSFORME. Thanks!
- http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Whiteboard: CLOSEME 07/14
Version: unspecified → Trunk
Reporter | ||
Comment 4•17 years ago
|
||
The problem still remains. It is related to the use of the attribute "display: float;" on an object that has too many floating objects inside it.
This example still remains: http://www.lostadam.net/trainer/test.html
Comment 5•17 years ago
|
||
I'm unable to reproduce this with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a6pre) Gecko/20070626 Minefield/3.0a6pre ID:2007062604
Is this also reproducible for you if you use a new firefox profile?
- http://kb.mozillazine.org/Profile_manager
Due to lack of reporter feedback and the inability to reproduce this bug, it is
being resolved as INCOMPLETE. Reporter, feel free to reopen this bug if you
still are experiencing this issue and wish to provide us with more information
so that we can help.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•