Make WordPress Core

Opened 7 months ago

Closed 6 months ago

#62173 closed defect (bug) (wontfix)

Blank Page Appears When Switching Pages in WordPress Editor

Reported by: parinpanjari's profile parinpanjari Owned by:
Milestone: Priority: normal
Severity: major Version: 6.6.2
Component: Editor Keywords: needs-patch has-testing-info has-screenshots
Focuses: ui, accessibility Cc:

Description

Summary:
When switching between pages in the WordPress editor, the screen goes blank, and I had to reload the page to see the data again.

Steps to Reproduce:

Open WordPress editor (Appearance > Editor > Pages).
Switch between different pages.
Notice that the page goes blank.
The user has to reload the page for the content to reappear.

Expected Behavior:
The page should load the content immediately when switching between pages without needing a reload.

Actual Behavior:
The page goes blank, and the user has to reload it to display the content.

Environment Details:

Chrome Browser Version: 129.0.6668.90 (Official Build) (x86_64)
Operating System: macOS Sonoma Version 14.5 (23F79)
Active Theme: Twenty Twenty-Four
Plugins Activated: None
WordPress Version: 6.6.2

Video Recording: https://www.loom.com/share/e7496ba592b14d2595f6703fef376a18?sid=57ea43fc-c9a0-4eab-98e7-4f99c7de3608

Change History (7)

This ticket was mentioned in Slack in #core-test by parinpanjari. View the logs.


7 months ago

#2 @sumitbagthariya16
7 months ago

I tried to reproduce the issue and encountered the same problem.

https://i.giphy.com/media/v1.Y2lkPTc5MGI3NjExdWdnbXlpcTJ1emFjOTFwMjQ5Y3RrbjRqc2s3ZnF5NHN6djcwdHp5cSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/Yk12UTCxPNXMv4Gh3E/giphy.gif

#3 @nithins53
7 months ago

I am also able to replicate the issue on WordPress 6.6.2. This issue is not there on WordPress 6.7 Beta 1.

#4 @ugyensupport
7 months ago

I would agree with @nithins53 not seen with WordPress 6.7 Beta 1

#5 @ironprogrammer
7 months ago

  • Keywords has-testing-info has-screenshots added; needs-testing removed
  • Milestone changed from Awaiting Review to 6.6.3

Thanks, everyone, for testing this! I was also able to reproduce this in Chrome for 6.6.2 (using Playground or a local install), but not in 6.7-beta, as confirmed by others above. Safari and Firefox did not produce the issue in either version.

As this seems to only affect 6.6, I've moved it into the 6.6.3 milestone for consideration. The minor release squad will monitor reported issues to determine if and when another minor might be released. I'll also raise this ticket in the #6-6-release-leads channel.

Environment

  • Hardware: MacBook Pro Apple M1 Pro
  • OS: macOS 14.6.1
  • Browser: Safari 17.6, Google Chrome 129.0.6668.91, Mozilla Firefox 130.0.1
  • Server: nginx/1.27.1 / PHP: 8.3.12 / MySQL: 8.0.27 AND WordPress Playground
  • Theme: twentytwentyfour v1.2

Test Playground Links (compare Chrome with other browsers)

This ticket was mentioned in Slack in #core by joemcgill. View the logs.


7 months ago

#7 @desrosj
6 months ago

  • Milestone 6.6.3 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Based on the testing results above, it seems this is no longer an issue in 6.7 and the issue is also intermittent.

There are currently no plans to have a 6.6.3 release at this time. And with RC1 for 6.7 happening in a few hours, I think it's best to just close this out as wontfix.

If this surfaces as a larger problem than it currently presents as, we can reopen this and reconsider.

Note: See TracTickets for help on using tickets.