User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031030 If the layout is using a table to display the web page, and a lot of content required, the table layout is not right. First column is displayed with width=100%. Sometimes, a simple refresh is fixing, sometimes not... Bug with FireFox and Mozilla. Looks like it's only happening if the internet connection is too slow in regard of the content. Local tests or very fast internet connection (faster as ADSL) don't reproduce this bug. Reproducible: Sometimes Steps to Reproduce: 1. Go to etalkers.org (Maybe you will see immediatly the problem, if not go to step 2) 2. Register as member (free of course, no spam or other disadvantage ;) ) 3. Use the usertheme menu on the left side to switch to an other graphical theme or/and navigate on the site Actual Results: First column of the main table is displayed with width: 100% Expected Results: First column width should be 150 pixels or 15% of the screen ONLY.
Bugs that occur in both Mozilla and Firefox should be filed in the Browser component. -> Browser:Layout
Assignee: firefox → nobody
Component: General → Layout
Product: Firefox → Browser
QA Contact: firefox.general → core.layout
Version: unspecified → Trunk
Is this a problem with a current build? 1.6a is ancient...
This issue is existing with ALL Moz/FireFox versions. Just try the reproducible process. ;) Just here to report this bug I didn't upgrade to keep an old version for tests. Thanks for your nice work guys ;)
Work around (But NOT the fix) is: add an empty row at the beginning of the table with correct sizes to use... Fixed on my site, so if you need to see the bug on my site (you can anyway see on many other sites ;) ), please ask me to reinstall old layout.
I have the same Bug on my side, by using the cms system "e107.org". I tryed the Row Trick but it won't fix it on my side. MozTeam! PLZ Help us out with a littel Fix :) Greez WrYBiT
I'm using 1.0.1 and this still happens
Same problem for me using Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Not every time but more on some sites than others.
The setting nglayout.initialpaint.delay used to fix this error. You had to set it to about 1500 milliseconds, but it would make firefox render pages correctly. Now this setting has been taken out in current builds. I'm not sure if adding it back is the correct fix but it seemed to do the trick for me.
I'm seeing this problem on e107 sites with the more popular themes, and now I'm seeing this on politics.slashdot.org
I am expereincing the problem on Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 This is very bandwidth dependent. (confiming some info floating around)
(In reply to comment #10) > I am expereincing the problem on > Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 > This is very bandwidth dependent. > (confiming some info floating around) (In reply to comment #10) > I am expereincing the problem on > Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 > This is very bandwidth dependent. > (confiming some info floating around) I have been a member of this community for some time..http://www.bbc.co.uk/dna/h2g2/ I recently noticed that occasionally, when viewing a page at this site in Firefox, a horizontal scroll bar appears at the bottom of the page -- similar to the one that appears at the bottom of the mis-rendered e107 pages. Scrolling the window to the right reveals about 1/2 page of background, however no content is hidden in this area, as is the case with e107 content pages. The h2g2 site has undergone a couple of upgrades, and I thought it was a minor bug with their system. However, viewing the page in IE doesn't result in a superfluous horizontal scroll bar. ( I rarely use IE anymore, btw, so I never really paid much attention to this display anomaly )
I don't see a problem with politics.slashdot.org and e107.org has changed please reopen if you can reproduce and attach or specify a testcase, preferably in minimal form
You need to log in before you can comment on or make changes to this bug.