-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
NS_ERROR_FAILURE in Firefox for every keystroke in Custom Element #1000
Comments
First @csuwildcat congrats on owning issue #1000 . So, I've run into this issue quite a few times with firefox. Generally, when I've gotten the dubious If you were able to narrow it down to this line, could you debug and just call |
I have the same issue - I called document.getSelection() and the focus was definitely in the right element. The error occured for me when I pressed return (shift + return was fine). The lines of code that caused the error for me were as below, but it was browserified and uglified so it's a bit hard to pin down:
|
This may have been a duplicate of #994 , and thus could have been fixed by #1052 (and available starting with version 5.16.1 of medium-editor) @NickBlow or @csuwildcat could you test out the newest version of medium-editor and see if this issue has been resolved for you? |
I get this issue when using the editor with Angular. Error happens only when using the ordered list and unordered list buttons side the function function |
I'm experiencing this issue with medium-editor 5.23.2 and Angular 1.6.6. |
Ah okay, so it appears that my issue is that my editor is on a Line 109 in c619e75
Is there a reason, why |
I have wrapped Medium Editor in a generic Web Component Custom Element (
<x-medium-editor>
is the node the editor is instantiated on) which somehow causes Firefox to throw an error every time the user enters text. When pressing enter, the entire outerHTML is duplicated resulting in a copy of the editor element itself. Here's the code point flagged in dev tools:The text was updated successfully, but these errors were encountered: