-
Notifications
You must be signed in to change notification settings - Fork 13
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
Hotkeys: prevent contenteditable
tags from behaving properly
#558
Comments
Interesting. I wasn't aware of this attribute. Link for reference https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/contenteditable We should modify our code at Lines 53 to 77 in 1950a82
contenteditable and skip triggering our events in that case.
|
contenteditable
tags from behaving properly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details
Expected Result
When using
contenteditable
tags in my documentation, I expect keyboard inputs to be available to a user on my site.Actual Result
Given ReadTheDocs makes use of several
EventListener
s for hotkeys, the letterd
does not work as expected as a user input in acontenteditable
tag.This has resulted in buggy behavior in a MkDocs plugin I am working on, as documented in the issue here: samgaudet/mkdocs-madlibs#4 (comment)
Reproduce the issue
To reproduce the issue, navigate here, click the editable
NAME
field, and try to type a name that includes the letterd
.Solution ideation
As far as I have been able to tell, there is not easy way to toggle the
EventListener
off or remove it for my documentation site. Perhaps one solution may be to allow for easier configuration ofEventListener
s and/or hotkeys from within a Read the Docs project's configuration/settings?The text was updated successfully, but these errors were encountered: