Closed
Bug 1379553
Opened 7 years ago
Closed 7 years ago
stylo: some Google Drive context menu items are missing
Categories
(Core :: CSS Parsing and Computation, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: cpeterson, Assigned: bradwerth)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
447 bytes,
text/html
|
Details |
STR: 1. Load a Google Drive folder, such as https://drive.google.com/drive/u/0/folders/0B2A4dciB6g1cbGxWdnIwNU5obUk 2. Right-click on a Google Doc in the folder to open the context menu. 3. Mouse-over the context menu's "Open with" sub-menu. RESULT: When Stylo is enabled, the context menu's "Remove" menu item is missing, the "Download" menu item's text is faded, and the "Open with" sub-menu is empty (instead of showing "Google Sheets"). I am testing Stylo in Nightly 56.0a1 (2017-07-09) on Windows 10.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → bwerth
Assignee | ||
Comment 1•7 years ago
|
||
The relevant property which is displaying poorly is: background: rgba(0, 0, 0, 0) linear-gradient(rgba(255, 255, 255, 0) 0%, rgb(255, 255, 255) 50%) repeat scroll 0% 0%; Could possibly be reduced further. Will build a reftest.
Assignee | ||
Comment 2•7 years ago
|
||
(In reply to Brad Werth [:bradwerth] from comment #1) > The relevant property which is displaying poorly is: > > background: rgba(0, 0, 0, 0) linear-gradient(rgba(255, 255, 255, 0) 0%, > rgb(255, 255, 255) 50%) repeat scroll 0% 0%; The actual problem appears to be that the gradient is not animated away as it should be. Still isolating the specific animation styles.
Comment 3•7 years ago
|
||
CCing animation people. Thank you Brad for the great analysis!
Comment 4•7 years ago
|
||
Hi Brad, are you still working on this? (It's assigned to you and comment 2 suggests you are, but I didn't see it in your recent mail to stylo-team so I thought I'd check.)
Flags: needinfo?(bwerth)
Assignee | ||
Comment 5•7 years ago
|
||
I haven't made much progress recently -- still working to reduce a testcase. I believe it to be due to some combination of animation styles and ::after pseudo-element content. Feel free to reassign the bug, as I'm unlikely to solve it before my upcoming time off.
Flags: needinfo?(bwerth)
Assignee | ||
Comment 6•7 years ago
|
||
If I am correct that this problem is due to animation/transition styles not working well with pseudo-elements, then Bug 1381670 has a simplified testcase.
Assignee | ||
Comment 8•7 years ago
|
||
Getting closer. Steps to Reproduce: 1) Load the testcase. After the animation of the white gradient, you will see the expected blue rectangle. 2) Open the devtools panel. 3) Reload. After the animation, the white gradient will pop back in on top of the blue rectangle. On the actual Google Drive site, this unexpected behavior happens even when devtools panel is not open.
Assignee | ||
Comment 9•7 years ago
|
||
Reduced further to a forwards animated z-index property on an ::after pseudo-element. Steps to reproduce: 1) Load the testcase. The red rectangle will change to a blue rectangle. 2) Open Devtools Inspector or Style Editor (other panels will not trigger bug). The blue rectangle will incorrectly change back to a red rectangle. Again, on Google Drive, the incorrect behavior is observed during normal site navigation, not linked to use of Devtools.
Attachment #8887574 -
Attachment is obsolete: true
Comment 10•7 years ago
|
||
I think this might be fixed by bug 1367278.
Comment 11•7 years ago
|
||
I've confirmed that the patch for bug 1367278 fixes this issue.
Depends on: 1367278
Comment 12•7 years ago
|
||
Chris, could you please double check this issue does not happen on the latest nightly (20170722112649)?
Flags: needinfo?(cpeterson)
Reporter | ||
Comment 13•7 years ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #12) > Chris, could you please double check this issue does not happen on the > latest nightly (20170722112649)? Yep! The context menus work correctly for me in build 2017-07-23. I will resolve this bug as fixed by bug 1367278.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(cpeterson)
Resolution: --- → FIXED
Updated•7 years ago
|
status-firefox56:
--- → fixed
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•