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 on card elements should not intercepted by the editor #114

Closed
dtetto opened this issue Sep 4, 2015 · 1 comment · Fixed by #115
Closed

Events on card elements should not intercepted by the editor #114

dtetto opened this issue Sep 4, 2015 · 1 comment · Fixed by #115
Assignees

Comments

@dtetto
Copy link
Member

dtetto commented Sep 4, 2015

When editing a card within its element (say, typing in an injected textarea or input) the editor’s behavior intercepts and prevents events like backspacing and pasting. The editor’s callbacks don’t need to fire while using in-card UI, and DOM events within the card should not be prevented/intercepted (maybe no DOM events should bubble out of the card element by default?).

@bantic
Copy link
Collaborator

bantic commented Sep 4, 2015

Ah, yeah, thanks for reporting. I recently refactored the listener code (in #113) to flow through a single event handling function, which should make it easier to stop all event handling when the user is in a sub-UI like a card. This should be straightforward to fix.

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

Successfully merging a pull request may close this issue.

2 participants