Closed Bug 2686 Opened 26 years ago Closed 26 years ago

[PP]1/26: Bigger font displayed for links in top banner and page footer

Categories

(Core :: CSS Parsing and Computation, defect, P3)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
All
Windows NT
Type:
defect

Tracking

()

Status:
CLOSED INVALID

People

(Reporter: gerardok, Assigned: peterl-retired)

References

(
URL
)

Details

Version: 5.0 (Seamonkey)
Build: Jan_26
Platform: Win NT 4.0 & Linux RedHat kernel 2.0.36

Description:
Fonts used for links in top banner and page footer, and date in the right column
are larger than when they're displayed in Communicator 4.50 or IE 4.0.

The same issue happens on Linux.

Steps to reproduce:
1. From the Browser, load the page for above URL

Result: Big fonts displayed
Expected: Smaller fonts as displayed in 4.5 or IE 4.0
Assignee: michaelp → peterl
Component: Rendering → Style System
Summary: [PP]1/26: Bigger font displayed for links in top banner and page footer → [PP]1/26: Bigger font displayed for links in top banner and page footer
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
Not a bug. This is due to us no longer emulating Nav's font rounding bug.
The font size=-2 should be 8 points (if the default size is 12 points). We
render this as 8 points. Nav renders 8 point text at 7 points on windows.

IE uses a different font scaling algorithm for determining the size of size=-2,
so they happen to align with Navs buggy size. This is coincidental.
Inserting Milestone info.
QA Contact: 4015
GErardo, please mark VERIFIED_FIXED  if it is..
GErardo, please mark VERIFIED...oops not fixed...VERIFIED_WONTFIX...
Status: RESOLVED → REOPENED
Resolution should be INVALID (The problem described is not a bug) instead of
WONTFIX (The problem described is a bug which will never be fixed). Reopening
bug...
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: WONTFIX → INVALID
Resolution changed to INVALID.
Status: RESOLVED → CLOSED
Marking bug as CLOSED.
You need to log in before you can comment on or make changes to this bug.