Closed
Bug 295370
Opened 20 years ago
Closed 17 years ago
prserv.net - Page renders incorrectly in FF 1.0.4. Renders OK in Mozilla 1.7.8
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: rsw0603, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Fonts and menu items render incorrectly on this page using Firefox 1.0.4. This was tested on two separate WinXP systems with the same result. On a WinXP (SP2) system with both Mozilla 1.7.8 and Firefox 1.0.4 installed, the problem appears only with Firefox and not with Mozilla. The rest of the AT&T Business site (http://www.attbusiness.net) renders correctly in both browsers. MSIE6 renders the same as Mozilla 1.7.8. The systems were also tested with all virus protection and firewalls temporarily disabled, with no change in behavior. Reproducible: Always Steps to Reproduce: 1. Start browser. 2. Navigator to the following URL: https://services.prserv.net/svc?p201=ATT&type=UFAF 3. Switch back and forth between the Home page and the Account pages. Actual Results: This page and all other links from this page(fonts, displayed text) do not render the same as the rest of the site with FF 1.0.4, but do render correctly using Mozilla 1.7.8 and MSIE6. Expected Results: Page should render the same in both Firefox and Mozilla.
Comment 1•20 years ago
|
||
Please test a current Firefox trunk build. 1.0.4 is to old to report gecko bugs (The gecko in FF1.0.X is over one year old) http://mozilla.osuosl.org/pub/mozilla.org/firefox/nightly/2005-05-24-06-trunk/
Comment 2•20 years ago
|
||
I see this as well with a trunk build. Its seems like different browsers get different html. IE and Opera get css for the menu, Firefox doesn't. One other note, though i dont think that is the issue, is that the html is horrible. The body tag comes first, then after it, comes the DOCTYPE.... --> Tech Evangelism
Assignee: nobody → english-us
Component: General → English US
Product: Firefox → Tech Evangelism
QA Contact: general → english-us
Summary: Page renders incorrectly in FF 1.0.4. Renders OK in Mozilla 1.7.8 → prserv.net - Page renders incorrectly in FF 1.0.4. Renders OK in Mozilla 1.7.8
(In reply to comment #1) > Please test a current Firefox trunk build. 1.0.4 is to old to report gecko bugs > (The gecko in FF1.0.X is over one year old) > > http://mozilla.osuosl.org/pub/mozilla.org/firefox/nightly/2005-05-24-06-trunk/ Maybe I'm mistaken, but 1.0.4 is the current release. It was made available on May 11, 2005 -- less than two weeks ago, not a year ago. Please also note that both Firefox 1.0.4 and Mozille 1.7.8 use the same Gecko 1.7.8 rendering engine. The current release of Mozilla renders correctly, but the current Firefox release does not (even on the same PC with both browsers installed). This seems to be a problem unique to Firefox. I haven't checked whether this problem exists in the nightlies, but since it is in the released version and I could find no duplicate report, I thought it was worth reporting here, even if it turns out to be a site-specific issue. Thanks.
Comment 4•20 years ago
|
||
(In reply to comment #3) > Maybe I'm mistaken, but 1.0.4 is the current release. It was made available on > May 11, 2005 -- less than two weeks ago, not a year ago. Yes, but Firefox 1.0.x is based on gecko 1.7, a layout engine older than one year now. Firefox nightlies and the upcoming Firefox 1.1 is based on gecko 1.8. It is therefore pointless to file layout bugs with Firefox 1.0.x Anyway, this is not a Firefox issue, its a website issue.
(In reply to comment #4) > (In reply to comment #3) > > Maybe I'm mistaken, but 1.0.4 is the current release. It was made available on > > May 11, 2005 -- less than two weeks ago, not a year ago. > > Yes, but Firefox 1.0.x is based on gecko 1.7, a layout engine older than one > year now. Firefox nightlies and the upcoming Firefox 1.1 is based on gecko 1.8. > It is therefore pointless to file layout bugs with Firefox 1.0.x Thank you for the clarification. I suppose I have a newbie question. If this is not the appropriate place to report (perceived) bugs in the official released products, then where should they be reported? I'm not a developer and don't have any interest in trying out the untested nightly builds, but I am a loyal Mozilla user and think that bugs in the production code found by ordinary users like me need as much visibilty as bugs in code under development. Thanks for any advice/suggestions for how I can participate in the process of making Firefox an even better browser.
Comment 6•20 years ago
|
||
Bugzilla is a bug tracking tool for the Mozilla.org developers. We need bug reports from the users but only if they are usefull. Firefox1.0.4 is basically only Firefox1.0 plus additional security fixes. The Gecko in FF1.0 is over 12+ months old and it doesn't help to report Gecko bugs from such old builds unless they can be reproduced in a current nightly Build. The reason: Many of the reported bugs in the FF1.0.X Gecko are already fixed in the trunk.
Comment 7•20 years ago
|
||
A user's comment: after updating from FF1.0.3 to 1.0.4 some form-elements were rendered incorrectly. Notice the select box in the center at http://www.uni-salzburg.at/studium/studienbeitrag/beitragshoehe/ and look at its text size. It is 11px textsize and 15px height of the box. FF1.0.4 ignores the font-size of text. Same behavia with the textboxes at the upper left. I returned back to FF1.0.3 (new setup at the same computer) and rendering is correct. hth for developing - greetings Siegfried
Comment 8•17 years ago
|
||
INCOMPLETE, as the page requires a login we don't have and is unlikely to be a problem three years later after multiple site redesigns.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•