New Lightbox (expand on click) does not work in WordPress 6.4 Beta 1

[burnuser]

Description

No Lightbox at all
Maybe (?) in conjunction with the usual layout error of Beta version, seen in navigation:

Step-by-step reproduction instructions

1. Make a fresh WordPress installation.
2. set "sample page" as Homepage
3. Install Beta Plugin
4. select Bleeding Edge version
5. update wordpress
6. insert an image
7. select "expand on click"
8. view page
9. see image and try to click => ?

Screenshots, screen recording, code snippet

Regular page without Lightbox:

Page with "expand on click":

Click on grey area opens image at the bottom of the page:

Environment info

• WordPress: 6.4-beta1-56730
• PHP: 8.1.23
• Server: nginx/1.16.0
• Database: mysqli (Server: 8.0.16 / Client: 8.1.23)
• Browser: Chrome 117.0.0.0 (Windows 10/11)
• Theme: Twenty Twenty-Three 1.2
• MU-Plugins: Keine aktiviert
• Plugins:
  • WordPress Beta Tester 3.5.4

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[jordesign]

Hey @burnuser - I'd seen that general layout error in testing 6.2 as well - does it (or the lightbox issue) go away when the Gutenberg plugin is installed and active?

[jordesign]

In my testing of the beta - I'm getting the expand/lightbox operating as expected - so I wonder if there's something else at play here. We may need to narrow things down further.

[burnuser]

@jordesign

1.) Test with Gutenberg to Beta added and activated:
a) general layoutbug is gone
b) lightbox works

Gutenberg deactivated (Beta alone):
both errors are back again

2.) Test with fresh environment: WP 6.3.1 + Gutenberg:
no layoutbug + lightbox works

Result: problem must be located in Beta

[michalczaplinski]

cc: @artemiomorales

[artemiomorales]

Has anyone else been able to reproduce this? I'm unable to replicate.

CC
@burnuser
@michalczaplinski

[carolinan]

While not a long-term solution, does it work if you set define( 'SCRIPT_DEBUG', true ); in wp-config?

[burnuser]

Test with local WP environments (which I - and many other people around the world - use for development and testing) - using http:
Laragon: https://laragon.org/
Local: https://localwp.com/
=> both show the described bugs

Test with 2 Online environments - using https:
InstaWP
TasteWP
=> no bug visible

[t-hamano]

Considering that this problem occurs on a site built on a local Windows OS machine, does not occur on a site built using InstaWP, etc., and the screenshot posted in the issue, it is the same as the problem reported in #54849. Therefore, I would like to close this issue.

A description of the cause for this problem and a patch to resolve it can be found in this core ticket: https://core.trac.wordpress.org/ticket/59489