Closed
Bug 268528
Opened 21 years ago
Closed 20 years ago
Rendering issues and non-functioning links
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: drcowsley, Unassigned)
References
()
Details
(Keywords: qawanted)
User-Agent: Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Win98; rv:1.7.3) Gecko/20040913 Firefox/0.10
The referred page was designed by an IE user with at least some thought for
other browsers. I am not qualified to say how well, not to identify which if
any of the reported bugs it has, nor whether it reveals any new ones.
The page is, unfortunately, in an opinion-forming position. My inability to
explain the differences eroded my credibility in spreading the Firefox message.
A quick comparison with the IE rendering reveals the layout differences. A
check on the 'clever' links at the top of the sidebar and across the main frame
shows they work in IE but not in Firefox.
Reproducible: Always
Steps to Reproduce:
1.Load page in IE, load page in Ff
2.Look at rendering difficulkties
3.Click on Events, Related Links, About us, Calendar, Departments etc.
Actual Results:
Ff links don't work, layout is a mess
Expected Results:
Would be easier to sell Ff if it worked. Next best is to be able to say the
page is wrong html so browsers won't necessarily work - the author got it to
work with IE but not Ff
Updated•21 years ago
|
Assignee: firefox → general
Component: General → Browser-General
Keywords: qawanted
Product: Firefox → Browser
QA Contact: firefox.general → general
Version: unspecified → Trunk
Comment 1•21 years ago
|
||
The page uses at least some IE-specific script (see JS console when clicking on
the links), as well as some invalid CSS (negative paddings) and the like...
It may be worth breaking this bug up into separate issues for separate problems
on the site, but I have a sneaking suspicion they'll all end up invalid.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 2•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•