[wp-trac] [WordPress Trac] #60088: Visual Editor can't select text Chrome Beta, Dev, Canary and Chromium

WordPress Trac noreply at wordpress.org
Tue Feb 13 12:29:29 UTC 2024


#60088: Visual Editor can't select text  Chrome Beta, Dev, Canary and Chromium
----------------------------+------------------------
 Reporter:  rybtechsupport  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Editor          |     Version:  6.4.2
 Severity:  critical        |  Resolution:  duplicate
 Keywords:                  |     Focuses:
----------------------------+------------------------

Comment (by ecuzebagixaw1982):

 Thank you for bringing this issue to our attention. The inability to
 select text in the Visual Editor of WordPress while using Chrome Beta,
 Dev, Canary, and Chromium browsers is indeed a significant problem that
 can hinder productivity and user experience for many WordPress users. Your
 detailed description of the issue, including multiple instances across
 different computers and versions of Chrome, suggests that this is a
 widespread and persistent issue that needs to be addressed promptly.

 Based on your description, it seems that this issue is specific to the
 Visual Editor in WordPress and is not affecting other parts of the
 WordPress admin interface or other websites in the Chrome Beta, Dev,
 Canary, and Chromium browsers. This indicates that the problem is likely
 related to the interaction between the Visual Editor and the browser
 environment rather than a general issue with text selection in Chrome.

 Given that the problem started occurring about a week ago after updates to
 Chrome Beta, Dev, Canary, and Chromium, it's possible that the updates
 introduced a compatibility issue or bug that is affecting the
 functionality of the Visual Editor. It's also worth considering whether
 any recent changes to the WordPress core or plugins could be contributing
 to the issue.

 To address this problem, there are several steps that can be taken:

 1. **Report the Issue**: It's essential to report this issue to both the
 WordPress development team and the Chrome development team. Providing
 detailed information about the problem, including browser versions,
 operating system, and any relevant error messages, can help developers
 identify and fix the issue more effectively.

 2. **Temporary Workarounds**: While waiting for a permanent solution,
 users affected by this issue can consider using alternative browsers or
 the Classic Editor plugin as a temporary workaround. The Classic Editor
 provides a familiar editing experience similar to the previous WordPress
 editor and may not be affected by the same compatibility issues.

 3. **Monitor for Updates**: Keep an eye on updates for both WordPress and
 Chrome to see if any patches or fixes are released to address this issue.
 It's possible that future updates to either the browser or the WordPress
 core could resolve the problem.

 4. **Check for Plugin Compatibility**: If you're using any plugins or
 themes that interact with the Visual Editor, make sure they are compatible
 with the latest versions of WordPress and Chrome. Incompatibilities with
 third-party code could exacerbate the issue.

 5. **Consider Browser Settings**: Review browser settings and
 configurations to see if any changes can mitigate the problem. This could
 include adjusting privacy settings, disabling extensions, or clearing
 browser cache and cookies.

 6. **Community Support**: Reach out to the WordPress community forums or
 relevant online communities to see if other users are experiencing similar
 issues and if any community-generated solutions or workarounds are
 available.

 In summary, the inability to select text in the Visual Editor of WordPress
 while using Chrome Beta, Dev, Canary, and Chromium browsers is a
 significant issue that requires attention from both the WordPress and
 Chrome development teams. By reporting the issue, exploring temporary
 workarounds, monitoring for updates, checking for plugin compatibility,
 reviewing browser settings, and seeking community support, affected users
 can work towards resolving the problem and restoring full functionality to
 the Visual Editor. Thank you for bringing this issue to our attention, and
 I hope these suggestions prove helpful in addressing the problem.

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


More information about the wp-trac mailing list