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

Events not being called #58

Open
catsalive opened this issue Jun 24, 2019 · 2 comments
Open

Events not being called #58

catsalive opened this issue Jun 24, 2019 · 2 comments

Comments

@catsalive
Copy link

catsalive commented Jun 24, 2019

  • Create vanilla aurelia-cli (1.0.1) project with following settings:
    image

  • Follow webpack instructions for this plugin

Problem:

  • froala-editor custom element never updates the bound value and no events are ever called

Update:
It appears that if the event listeners are added by specifying them in the config passed to the FroalaEditor class instead of adding them to the DOM element, then they are called appropriately.

@alexisszabo
Copy link

I created a pull request that should address this issue for Froala v3: #59

@Sayan751
Copy link
Contributor

@alexisszabo @catsalive I am also facing similar issues after upgrade. It seems that the event handlers for blur amd contentChanged are incorrectly applied on the DOM Element. Refer: https://github.com/froala/aurelia-froala-editor/blob/master/src/froala-editor.js#L67-L68

Whereas, those events seems to be Froala events.
Check the changes: b1940b6#diff-f44e1166524e0d158a08a9d294165ecdL64-R68
Froala event reference: https://www.froala.com/wysiwyg-editor/docs/events

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants