The default bug view has changed. See this FAQ.

two squares, supposed to be identical, have different edges

RESOLVED INVALID

Status

()

Core
Graphics
RESOLVED INVALID
10 years ago
10 years ago

People

(Reporter: Ray Kiddy, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
Created attachment 270537 [details]
pic of squares at very high resolution, showing fuzziness on left square

I am running on a 2.16 GHz Intel Core Duo with 10.4.9 and 2 GB memory.

This difference is a bit subtle, but it is obviously there. See the attachment, which is a snap of a Pixie window that shows the problem at a high resolution.

Load the page from the URL above. There are two squares.

On 2.0.0.4, these look very different. The left one has an empty center. On a trunk build, the squares look the same.

The squares do have a difference, though. The edges of the right-side square are very sharp and clear. The left-side box has a rim, 1 pixel wide, on the top, left and right side. Is there a reason the edges of these squares should be different?

Comment 1

10 years ago
On the left, the square is painted as a character (text anti-aliassing/shading), on the right the test is using the border-property.
I see the same fuzziness in all browsers (WebKit, Opera, iCab, Minefield,...) fwiw.

Comment 2

10 years ago
The testcase requires the Ahem font.

Comment 3

10 years ago
Yes, I know that (and I have that one installed). But that doesn't change anything. Even with the Ahem font, the OS level font-smoothing technology comes into action.

Updated

10 years ago
Assignee: joshmoz → vladimir
Flags: blocking1.9?

Updated

10 years ago
Assignee: vladimir → nobody
Component: GFX: Mac → GFX: Thebes
QA Contact: mac → thebes
What philippe said.  The glyph is getting FuzzyTyped(tm).
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Flags: blocking1.9?
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.