Opened 10 years ago
Closed 10 years ago
#30516 closed defect (bug) (fixed)
Focus v2: admin toolbar rendering issues
Reported by: | johnbillion | Owned by: | |
---|---|---|---|
Milestone: | 4.1 | Priority: | high |
Severity: | normal | Version: | 4.1 |
Component: | Editor | Keywords: | 2nd-opinion |
Focuses: | ui, administration | Cc: |
Description
When moving the mouse out of the editor (or tabbing out of it) after DFW has kicked in, the admin toolbar at the top of the screen fades back in but then all its content gets hidden.
This appears to be a rendering issue (not a CSS issue) because the items return when you move the cursor over the admin toolbar, or when DFW kicks in again.
Seen in Chrome 38 on OS X. Also tested in Firefox 33 on OS X with no issues.
Can anyone else reproduce?
Attachments (4)
Change History (21)
This ticket was mentioned in Slack in #feature-focus by janneke. View the logs.
10 years ago
This ticket was mentioned in Slack in #core by johnbillion. View the logs.
10 years ago
#5
@
10 years ago
Confirming that I've been seeing this too, Retina screen, Opera Chromium beta (Chrome/39.0.2171.62 Safari/537.36 OPR/26.0.1656.20).
#6
@
10 years ago
Perhaps as a hint to work out why/what is happening, the Notifications/Search icons remain on WordPress.com, whilst on a WordPress install, all (including the Jetpack Notifications icon) icons disappear, at least for me.
#7
@
10 years ago
Adding transform: translateZ(0);
to the .focus-off transition seems to clear up the issue in Chrome on retina screens.
#10
follow-up:
↓ 11
@
10 years ago
- Keywords 2nd-opinion added; needs-testing removed
I am a little concerned about any performance and stacking implications here - see http://stackoverflow.com/questions/10814178/css-performance-relative-to-translatez0. If we have to do this, it should likely be -webkit- only.
#11
in reply to:
↑ 10
@
10 years ago
Since we're only going for a repaint, and not trying to get hardware acceleration with this patch, we can simplify this to use a 2D transform: transform: translate(0, 0);
and avoid the issue Helen brings up.
30516.2.patch also adds the -webkit prefix.
Replying to helen:
I am a little concerned about any performance and stacking implications here - see http://stackoverflow.com/questions/10814178/css-performance-relative-to-translatez0. If we have to do this, it should likely be -webkit- only.
#12
@
10 years ago
30516.4.patch Fixes a display issue in Chrome where the right meta boxes would disappear when the content was long enough to make the page scrollable by moving the transform property so it only applies to the #wp-toolbar
.
Have seen this in Chrome 39 on OS X too.
See also https://github.com/avryl/focus/issues/15.