Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IE 10 and up: Language Switching Buttons do not change content in TinyMCE fields #115

Closed
johnclause opened this Issue Apr 3, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@johnclause
Copy link
Member

johnclause commented Apr 3, 2015

Apparently same issue reported in a few places:
https://wordpress.org/support/topic/unstable-under-ie11
https://wordpress.org/support/topic/buttons-dont-change-content-in-tinymce-fields-in-ie10-possible-fix

In short:

  1. The language switching buttons are, most of the time, not switching the content in TinyMCE.
    When editing content in WYSIWYG-area and updating the post, all changes are lost.
  2. A, sometimes, working solution is to switch to the raw editor and after that use the language switching buttons, or update the post. But this is inconsistent and not stable at all.
  3. No JS errors is reported in the F12 console.

Other user observation:

Not sure if this is actually a bug (maybe someone can confirm) or some plugin conflict BUT, after hacking away at admin/js/common.js I discovered the following:

  • window.addEventListener('load', function(){ ... }); works to register tinyMCE.editors in Chrome but not in IE (weird?)
  • "I have no idea what i'm doing but it's fixed": wrap everything up from inside the 'load' function in a setTimeout() with 1000 to give IE a chance to "LOAD" load the loaded page. (sheesh)

@johnclause johnclause added the bug label Apr 3, 2015

@johnclause

This comment has been minimized.

Copy link
Member Author

johnclause commented Apr 5, 2015

@johnclause

This comment has been minimized.

Copy link
Member Author

johnclause commented Apr 10, 2015

I assume this can be closed, we can still write into a closed issue, or we can re-open it, if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.