One pixel column error for display:none on plasmasturm.org

VERIFIED WORKSFORME

Status

()

Core
Layout
--
minor
VERIFIED WORKSFORME
10 years ago
4 years ago

People

(Reporter: Chris Dolan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b2) Gecko/2007121014 Firefox/3.0b2

Plasmaturm uses CSS a:hover to hide/show navigation titles.  When you hover over an anchor, an embedded span changes to display:inline and position:absolute.  When you mouse out, it switches to display:none.

For one of the navigation headers, the bit of the serif on a capital 'A' is left behind when the display:none goes into effect

Reproducible: Always

Steps to Reproduce:
1. go to http://plasmasturm.org/
2. hover over the "?" symbol in the top right
3. see the "About" title appear
4. mouse off the "?"

Actual Results:  
The leftmost pixel column remains, showing a bit of the white serif of the "A"

Expected Results:  
No remnant of the title should appear
(Reporter)

Comment 1

10 years ago
Created attachment 299584 [details]
Screenshot showing the artifact
(Reporter)

Comment 2

10 years ago
Oops, I forgot to add: I tested this in Safari to ensure it was not a problem with the font itself.  Safari renders it correctly.  I did not explicitly test Firefox 2.x, but I've been on plasmasturm.org enough that I would have noticed it if the render problem had existed on that Gecko version.
Summary: One pixel column error for display:none on plasmaturm.org → One pixel column error for display:none on plasmasturm.org
Component: General → Layout
Keywords: qawanted
Product: Firefox → Core
QA Contact: general → layout

Comment 3

10 years ago
WFM using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5 ID:2008032620
I was able to reproduce this bug only on: 
1. Firefox 3.0b1: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9b1) Gecko/2007110903 
2. Firefox 3.0b2: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9b2) Gecko/2007121014 
using Mac OS X 10.6.8. 

The following other builds were used for testing this issue, but it was *not* reproducible on them:
- Firefox 2.0.0.17 (RC),
- Firefox 3.0b3 (Beta 3),
- Firefox 3.0 (RC),
- Firefox 3.5.1 (RC),
- Firefox 27.0a2 (latest Aurora).

It's safe to say that this issue is no longer reproducible starting with Beta 3 of Firefox 3.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Keywords: qawanted
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.