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

p-editor - HTML binding fails #10081

Closed
dloprodu opened this issue Apr 6, 2021 · 2 comments
Closed

p-editor - HTML binding fails #10081

dloprodu opened this issue Apr 6, 2021 · 2 comments

Comments

@dloprodu
Copy link

dloprodu commented Apr 6, 2021

I'm submitting a ... (check one with "x")

[X] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Current behavior
When we have some browser extension, like Grammarly, the HTML binding fails, as you can see in the image below,

image

Expected behavior
The HTML binding should work, even if the user has some extension for the text areas installed.

Please tell us about your environment:

  • Angular version: 11.2.0
  • PrimeNG version: 11.3.0
  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

  • Language: [all | TypeScript X.X | ES6/7 | ES5]

  • Node (for AoT issues): node --version =
@yigitfindikli yigitfindikli added the Status: Pending Review Issue or pull request is being reviewed by Core Team label Apr 6, 2021
@yigitfindikli yigitfindikli removed the Status: Pending Review Issue or pull request is being reviewed by Core Team label Apr 19, 2021
@yigitfindikli
Copy link
Contributor

Unable to replicate with PrimeNG 11.3.2, if the issue persists please create a new ticket with a test case reproducing the issue e.g. stackblitz or a github repo and it will be reviewed by our team once again.

@dloprodu
Copy link
Author

dloprodu commented Apr 29, 2021 •
edited
Loading

@yigitfindikli the issue persists. The problem is the higlighted line in red in your code. You have to select by class (.ql-editor), no select the first element (because the first element could be an extension). I think the problem is very clear.

image

@dloprodu dloprodu mentioned this issue Apr 30, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dloprodu @yigitfindikli