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.

Sign up for GitHub

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

Jump to bottom

Tinymce: error in [unknown object].fireEvent(): event name: tinymceChange error message: URI malformed #9452

Closed
hostep opened this issue Apr 28, 2017 · 3 comments
Closed

Tinymce: error in [unknown object].fireEvent(): event name: tinymceChange error message: URI malformed #9452

hostep opened this issue Apr 28, 2017 · 3 comments
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@hostep
Copy link
Contributor

hostep commented Apr 28, 2017

Preconditions

  1. Magento develop branch (tested with revision: 5ea676e)
  2. PHP 7.0.18

Steps to reproduce

  1. Setup a brand new Magento project from the develop branch
  2. Login to the backend
  3. Go to Content => Pages
  4. Create a new Page
  5. In the Content field, start entering: 10%

Expected result

  1. No errors should pop up

Actual result

  1. From the moment you type the % character, an error pops up:
    error in [unknown object].fireEvent(): event name: tinymceChange error message: URI malformed

screen shot 2017-04-28 at 20 55 54

Discussion

This problem was introduced in this commit: 9030e08
Removing the line content = decodeURIComponent(content); fixes the issue.

The question is: why was the line added?
The commit was part of some other commits to fix issue #6138

But without that line, the issue is fixed as well, in my tests though, but maybe the line was necessary for some other edge case?

It would be great if this could be fixed before Magento 2.2 is released, as this is a really annoying problem :)

Thanks!
@hostep hostep mentioned this issue Apr 28, 2017
Closed
@shiftedreality
Copy link
Member

Internal ticket MAGETWO-66885

@hostep hostep mentioned this issue May 14, 2017
Closed
magento-team pushed a commit that referenced this issue Jun 12, 2017
@VladimirZaets
MAGETWO-66885: Special Characters like % in widget inside of WYSIWYG …
19a6485 
…gives an error #9452
magento-team pushed a commit that referenced this issue Jun 12, 2017
@MomotenkoNatalia
Merge pull request #1182 from magento-frontend/PR_08062017
d1b86ae 
Fixed issues:
- MAGETWO-61189: Stored xss using svg images in Favicon
- MAGETWO-54702: Failed ClearAllCompareProductsTest test due to Alert window.
- MAGETWO-66885: Special Characters like % in widget inside of WYSIWYG gives an error #9452
- MAGETWO-59514: Hard coded "tax_region_id" in the \Magento\Tax\Setup\InstallData
- MAGETWO-64952: Admin login does not handle autocomplete feature correctly
@hostep hostep mentioned this issue Jun 19, 2017
Closed
@veloraven
Copy link
Contributor

This issue was fixed in develop branch.
Closed.

hostep pushed a commit to hostep/magento2 that referenced this issue Jul 3, 2017
@VladimirZaets @hostep
MAGETWO-66885: Special Characters like % in widget inside of WYSIWYG …
3c14085 
…gives an error magento#9452

(cherry picked from commit 19a6485)
@hostep hostep mentioned this issue Jul 3, 2017
Closed
@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-70435

@magento-team magento-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Jul 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@hostep @magento-team @shiftedreality @veloraven