You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a post or page contains long content and triggers an insecure content warning, the page should automatically scroll to the top and highlight the error. Currently, if a post/page with long content has insecure content, after clicking the publish/update button, the user is unable to identify the cause of the failure because the warning appears at the top of the screen, which may not be visible due to the length of the content.
Recording.737.mp4
Steps to Reproduce
Steps to Reproduce:
Create or edit a post/page.
Add a significant amount of content to the editor to make the page scrollable.
Insert insecure content
Click the publish/update button.
Screenshots, screen recording, code snippet
Expected Result:
The page should automatically scroll to the top and highlight the insecure content warning, making it clear to the user why the post/page is not published.
Environment information
No response
WordPress information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
Description of the issue:
When a post or page contains long content and triggers an insecure content warning, the page should automatically scroll to the top and highlight the error. Currently, if a post/page with long content has insecure content, after clicking the publish/update button, the user is unable to identify the cause of the failure because the warning appears at the top of the screen, which may not be visible due to the length of the content.
Recording.737.mp4
Steps to Reproduce
Steps to Reproduce:
Screenshots, screen recording, code snippet
Expected Result:
The page should automatically scroll to the top and highlight the insecure content warning, making it clear to the user why the post/page is not published.
Environment information
No response
WordPress information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: