[wp-trac] [WordPress Trac] #59038: WordPress 6.3 Gutenberg Editor Bug - Editor Unusable

WordPress Trac noreply at wordpress.org
Mon Sep 11 13:16:44 UTC 2023


#59038: WordPress 6.3 Gutenberg Editor Bug - Editor Unusable
--------------------------+-------------------------
 Reporter:  sarahh1997    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.3.2
Component:  Editor        |     Version:  6.3
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:  javascript
--------------------------+-------------------------

Comment (by leehodson):

 There appears to still be a bug that shows when the Opera One browser is
 used to work with the Gutenberg editor. This bug looks similar to the one
 this Trac issue is about.

 Note: I posted above about the original issue this Trac discusses.

 The issue has been reported to Opera here
 https://forums.opera.com/topic/66015/opera-one-does-not-work-correctly-
 with-wordpress

 To summarise that bug (Opera One specific),

 - Using a non Incognito browser window causes Gutenberg to bug out
 - Sites where the bug shows itself do work fine when an Incognito browser
 window is used
 - The bug seems to be sporadic: it shows in some sites but not others
 - The bug appears not to be caused by WordPress plugins or themes
 - The bug appears not to be caused by Opera extensions
 - The bug (or maybe it is a different cause) affects the Appearance
 Customizer too: the Customizer loads but changes cannot be saved

 Note: Opera uses the term Private Window instead of Incognito Mode.

 I have fully cleared my browser cache and fully disabled browser
 extensions. The bug is there regardless.

 I suspect there is a difference in the way Opera One handles jQuery /
 Javascript errors between Private windows and plain non private windows.

 Console logs the same errors for this Opera One bug as it does for the
 fault discussed in this Trac thread, which is why I am posting about it
 here. I have checked Console with WP script debugging enabled and
 disabled. The Opera support forum thread includes an example of the
 Console errors (I am VR51 in that thread and on GitHub)

 Thought I would tag this observation onto this Trac issue and the Github
 issue I opened because it might shed light on the underlying cause of
 fault.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59038#comment:29>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list