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
WordPress 6.4 introduces lightboxing for images ("Expand on click"). There are two new issues here:
This is redundant now with our existing "Add lightbox effect" in the AMP Settings panel. We can now deprecate the AMP lightbox setting (and the AMP Settings panel entirely?) following up on Remove deprecated controls from editor sidebar and fix AMP Lightbox and AMP Carousel in Gallery block #6833. Block deprecation routines should automatically convert the AMP lightbox block attribute to the new core lightbox block attribute. This would only be applicable to Wordpress 6.4+. Note: There is also a site-wide option to enable lightboxing by default under Styles » Blocks » Images.
Core's lightbox functionality is breaking AMP validation. A new sanitizer or embed handler is needed to automatically convert lightboxed image blocks over to use the AMP lightbox functionality. So while the dedicated AMP UI for lightboxing should be removed in WP 6.4+, the underlying AMP lightbox sanitizer/embed code would remain and be reused now for implementing core's lightbox handling. Nevertheless, some changes may be needed to make the AMP implementation more in-line with what core is doing.
Bug Description
WordPress 6.4 introduces lightboxing for images ("Expand on click"). There are two new issues here:
Validation data for 4 validation errors
Expected Behaviour
Core image lightboxes should work on AMP pages without validation errors. There should not be redundant UI elements for lightboxing.
Screenshots
PHP Version
8.1
Plugin Version
2.5.0
AMP plugin template mode
Standard, Transitional, Reader
WordPress Version
6.4
Site Health
No response
Gutenberg Version
No response
OS(s) Affected
No response
Browser(s) Affected
No response
Device(s) Affected
No response
Acceptance Criteria
No response
Implementation Brief
No response
QA Testing Instructions
No response
Demo
No response
Changelog Entry
No response
The text was updated successfully, but these errors were encountered: