![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 6 years ago
Closed 6 years ago
#49213 closed defect (bug) (worksforme)
Hovering over Gutenberg toolbar buttons shows a weird arrow
| Reported by: | johnjamesjacoby | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Editor | Version: | |
| Severity: | normal | Keywords: | reporter-feedback close |
| Cc: | Focuses: | administration |
Description
When hovering over the Gutenberg toolbar buttons, sometimes (and for only a fraction of a second) a down arrow is visible in the top center of the screen.
Attachments (2)
Change History (7)
#2
@
6 years ago
- Keywords reporter-feedback added
Hi @johnjamesjacoby thanks for the report.
Testing on a clean trunk install I've been unable to reproduce the extraneous glyph.
Can you test a fresh install and let me know if you're still experiencing the issue? If so please provide your browser information along with any steps to reproduce consistently.
Thank you
#3
@
6 years ago
Can you test a fresh install and let me know if you're still experiencing the issue
Screenshot and movie are from a 5.3.2 install that was about 30 seconds old, so going to be hard to get much fresher than that.
I was able to replicate in all current versions of Chrome, Firefox, and Safari for macOS.
No plugins active. TwentyTwenty theme active.
Steps to replicate are essentially: Hover over the toolbar buttons and look at the top-middle for the flicker.
I will test on trunk and report back when I know more.
#4
@
6 years ago
- Keywords close added
Thanks for the information @johnjamesjacoby
Installing a 5.3.2 instance I was able to reproduce your issue. Following the same steps on trunk the issue doesn't present itself so I believe it's been resolved since 5.3.2. That being said it's hard to put your finger on it as it vanishes moments after it appears so I can't identify the dom element or js/css that's of cause.
If I'm able to determine a cause I'll try to trac down the changeset that resolved this bug.
I'm marking this ticket for close but leaving open for the time being in case you're able to reproduce on trunk or it re-surfaces during the 5.4 cycle here.
Video