-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NUX tips: Close button tooltip partially hidden on some tips #7562
Comments
Still can reproduce on current master |
Confirmed this is still an issue as of May 31, 2019. Debugging: It is caused by this style, specific to bottom popovers:
This was introduced in #5630 (cc @faishal, @karmatosed, @jorgefilipecosta). I don't think this style should have been introduced this way, since the fix considered for #5630 is very specific to a particular popover, and should not apply inherently to any bottom-oriented popover (evidenced by this bug). It occurs because the NUX popover and tooltip rely on a very specific relationship to place the tooltip above the NUX tip: gutenberg/assets/stylesheets/_z-index.scss Lines 104 to 108 in 1d2d1fc
The bottom-specific styling breaks this expectation, causing the tooltip to display below: gutenberg/assets/stylesheets/_z-index.scss Lines 90 to 92 in 1d2d1fc
|
#18041 has addressed this by removing dot tips in lieu of a welcome guide modal. |
When the "new user experience" tips are displayed, the tips Close button tooltip is partially hidden in some tips. To reproduce, for example in Chrome:
"GUTENBERG_NUX_1" if anyEdit: the storage mechanism has changed, you need now to clear the whole Gutenberg storage entryWorth noting the tooltip position is dynamically calculated to stay within the viewport, and that seems to work correctly. However, seems there's something wrong with the z-index. Not sure why when the popover takes the
is-bottom
class it gets a lower z-index.However, I guess the whole position of the tip should be reviewed, because the tooltip position conflicts with the pulsing dot.
The text was updated successfully, but these errors were encountered: