Opened 2 years ago
Closed 23 months ago
#57663 closed defect (bug) (reported-upstream)
Editor in 6.2 Beta 1: Shortcode-block missing styles on options
Reported by: | threadi | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.2 |
Component: | Editor | Keywords: | |
Focuses: | Cc: |
Description
Running the fresh 6.2 Beta 1 I found a confusing bug in the block editor on the shortcode-block. The options are missing its background and border.
Steps to reproduce:
- Create new page.
- Add Shortcode-block, nothing more.
- Click on the options if this block. It's hard to hit at first, on the 2nd or 3rd click it goes.
Happens with 6.2 Beta 1 without any active plugins.
Does not happen in 6.1.1 without any active plugins.
Does not happen to any other block I tested.
Activating Gutenberg 15.0.1-plugin it does not happen. Maybe this version is not yet included in the beta?
Used Firefox 109.0.1 on Windows.
Attachments (2)
Change History (7)
#1
@
2 years ago
- Milestone changed from Awaiting Review to 6.2
- Severity changed from minor to normal
#2
@
2 years ago
By the way, this should probably be reported on Gutenberg side, too: https://github.com/WordPress/gutenberg/issues
#3
@
2 years ago
I also reproduce the bug, by following the process,
Create new page.
Add Shortcode-block, nothing more.
Click on the options if this block.
Options are not coming on click in the shortcode block the first time, after several clicks options come but there is a kinda glitch effect. Please check the attachment.
Here is screencast also: https://d.pr/v/JGEL5u
Checked in WordPress 6.2-beta2
OS: Windows 10 version 22H2
Web Server: Nginx
PHP: 7.4.30
Browser: Chrome 109.0.5414.87
Theme: Twenty Twenty-Three
Active Plugins: No plugins activated.
This ticket was mentioned in Slack in #core by costdev. View the logs.
2 years ago
#5
@
23 months ago
- Milestone 6.2 deleted
- Resolution set to reported-upstream
- Status changed from new to closed
I am able to reproduce this on 6.2-beta2 but not on 6.2-beta3, so it looks like the fix was merged in Beta 3.
Unfortunately, I haven't found the specific commit that fixes this issue yet, but for now this ticket can be closed as reported-upstream
and the link to the bugfix commit can be added later when it's found.
Hello @threadi and thanks for opening this ticket!
Moving for 6.2 consideration as it was reported against 6.2 beta 1.