331832 - The text on the page is illegibly small

Status: RESOLVED DUPLICATE of bug 247365

(SeaMonkey :: General, defect)

Description

[Michael Graubart]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060127 SeaMonkey/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060127 SeaMonkey/1.0

I realize that this is about an ancient version of SeaMonkey (1.0), but as there have been no nightlies for about 6 weeks, it seems likely that it will apply to any new build that may be forthcoming, too. It is quite simple: the text onn this page is so small that it is virtually unreadable. In Safari and Internet Explorer, it is of normal, legible size.

Reproducible: Always

Steps to Reproduce:
1. Go to above website/webpage.
2. Try to read the text.


Actual Results:  
The text is almost illegibly small.

Expected Results:  
The text should be of normal size.

eMac G4, OS 10.4.5, Classic theme.

Comment 1

[zug_treno]

Related to/duplicate of bug 247365?

Comment 2

[Gérard Talbot]

This is definitely a coding issue with British airways site. I checked several files and I can see *_many_* problems with the coding practices used.

http://www.britishairways.com/cms/global/styles/core/interim.css
has well over 200 CSS classes (!) and has at least 10 classes where the declared font-size is under/smaller than 80%, which is small (like fine print) and not recommendable.

Also,
http://www.britishairways.com/cms/global/scripts/core/doc_man.js
which is another extremely long, complex and difficult to manage/maintain code page, is doing browser detect based on user agent string parsing and it's long and complex (and most likely wrong too for other browsers and marginal browsers) and also a very old one: it even tries to detect NS 3 and IE 3. And it makes false associations too. E.g.:

if (platform == "mac") {
if (browser_family == "ns6") whichStyle="mac_ns";
else whichStyle="mac_ie";
}

This webpage is definitely a case of Tech Evangelism to begin with. I doubt very much that the page would involve a Seamonkey browser bug for rendering font size.

Yes, zug_treno, checking with bug 247365 confirms all this.

Resolving as DUPLICATE of bug 247365

*** This bug has been marked as a duplicate of 247365 ***