WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36545, comment 18


Ignore:
Timestamp:
04/19/2016 03:43:32 AM (6 years ago)
Author:
doncullen
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36545, comment 18

    initial v1  
    1 Replying to [comment:2 azaozz]:
    2 > @doncullen: welcome to trac and thanks for the detailed bug report!
    3 >
    4 > Testing in both Chrome 49 and 50 (50.0.2661.75 m) on Windows 7, can't reproduce. Both reports are for Chrome 50.0.2661.75 beta-m so it's possible this was fixed in the stable release (that came out couple of days ago).
    5 >
    6 > The error points to TinyMCE's FocusManager: https://github.com/tinymce/tinymce/blob/master/js/tinymce/classes/FocusManager.js#L194-L216. There was a recent fix to that code as well: https://github.com/tinymce/tinymce/commit/544e9ff5482c8bab166bdf19dc45cbb7987547de.
    7 >
    8 > This fix, and TinyMCE 4.3.10 didn't make it in WordPress 4.5 as we were in RC at the time. However if the above bug is confirmed fixed there we should update TinyMCE in 4.5.1.
    9 >
    10 > Would appreciate more testing preferably in Chrome 50.0.2661.75 m on both Mac and PC.
     1I'm not sure why you're unable to reproduce, @azaozz ; but as you mentioned, it may be due to the issue being in the beta and having been resolved in the stable. Although @swissspidy's attempts seem to indicate that likely may not resolve the matter.
     2
     3In any case, I'd be happy to update my copy of the TinyMCE if you can let me know what the best way to do that would be.  I can apply the update and see if that resolves the issue.
     4
     5@afercia - indeed, I do have Chrome extensions, but I also tried it under Incognito mode to rule out that possibility (see original post), which usually disables all extensions, and still ran into the same error.