1380368 - stylo: site issue: visual bug with google docs star not visible until mouse over

Status: RESOLVED DUPLICATE of bug 1384065

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

Description

[Bryan Clark (DevTools PM) [:clarkbw]]

Attachment: before mouse over

In Google Docs the star is no longer visible until you mouse over it and then its visible and remains until reload.

Comment 1

[Bryan Clark (DevTools PM) [:clarkbw]]

Attachment: after mouse over

Comment 2

[Chris Peterson [:cpeterson]]

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.

Comment 3

[Xidorn Quan [:xidorn] UTC+11]

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...

Comment 4

[Bryan Clark (DevTools PM) [:clarkbw]]

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.

Comment 5

[Shing Lyu [:shinglyu]]

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.

Comment 6

[Shing Lyu [:shinglyu]]

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.

Comment 7

[Emilio Cobos Álvarez (:emilio)]

Likely a dupe of bug 1384065 too.

Comment 8

[Jeremy Chen ([e-mail])]

(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.