Closed
Bug 1380368
Opened 7 years ago
Closed 7 years ago
stylo: site issue: visual bug with google docs star not visible until mouse over
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
DUPLICATE
of bug 1384065
People
(Reporter: clarkbw, Assigned: shinglyu)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
In Google Docs the star is no longer visible until you mouse over it and then its visible and remains until reload.
Reporter | ||
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
I think I have seen a similar issue where mousing over some Google Docs buttons or the "Last edit was on ..." label would show a tooltip that would not disappear when I stopped mousing over. I could not reproduce it consistently so I wasn't able to determine if it was related to Stylo or just a Google Docs timing issue.
Blocks: stylo-site-issues
Priority: -- → P2
Comment 3•7 years ago
|
||
It seems to me that there is always a significant time before the star shows up, both in Gecko and Stylo, so I don't see any difference in this case...
Reporter | ||
Comment 4•7 years ago
|
||
The star doesn't show up in the stylo case, no matter how long I wait. I tested this with DevEdition and the star appears as soon as the other elements render.
Assignee | ||
Comment 5•7 years ago
|
||
I can reproduce this. The star never shows up in Stylo (until hovered), unlike Gecko which will eventually show up in a few seconds. I'll take a look into this.
Assignee | ||
Comment 6•7 years ago
|
||
The star is a ::before pseudo element with "content: url(//ssl.gstatic.com/ui/v1/star/star4.png);". In stylo the pseudo element is not created until hovered. The hover adds a "jfk-star-hover" class to the container element, creates the ::before pseudo element and loads a different png (star4-hover.png). Then the un-hover event will trigger the loading of the "star4.png" file. In Gecko the pseudo element is created on first load.
Updated•7 years ago
|
Assignee: nobody → shing.lyu
Updated•7 years ago
|
Comment 7•7 years ago
|
||
Likely a dupe of bug 1384065 too.
Comment 8•7 years ago
|
||
(In reply to Emilio Cobos Álvarez [:emilio] from comment #7)
> Likely a dupe of bug 1384065 too.
Yeah, you're right.
I can confirm this issue has been resolved in the latest Nightly 56.0a1 20170730100307 on Mac.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•