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

one approach to fix #258 and elegant #262 #286

Merged
merged 4 commits into from
May 17, 2015
Merged

one approach to fix #258 and elegant #262 #286

merged 4 commits into from
May 17, 2015

Conversation

houd1ni
Copy link

@houd1ni houd1ni commented May 12, 2015

Because of absence of other bad symptoms of reselecting code, based of ranges, I prefered just removing default handlers: remove and add Range, that, probably is less elegant way, but we can add own handler for CTRL events in future. More than, it fixes another found ctrl+a bugs, which I saw during debug. E.g. I couldn't select with ctrl+a after typing just "@jacob ", which, of course, has been generated by reselecting code.
Maybe, more beautiful way is creating something like '@vars' or '@pressed_btn' objects to handle that kind of variables, but now I prefered just delete them on the fly.
Tested in Chrome, ie11, mozilla.

just removing default handlers: remove and add Range, that, probably is
less elegant way, but we can add own handler for CTRL events. More than,
it fix another found ctrl+a bugs, which I saw during debug. E.g. I
couldn't select with ctrl+a after typing just "@jacob ".
just removing default handlers: remove and add Range, that, probably is
less elegant way, but we can add own handler for CTRL events. More than,
it fix another found ctrl+a bugs, which I saw during debug. E.g. I
couldn't select with ctrl+a after typing just "@jacob ".
just removing default handlers: remove and add Range, that, probably is
less elegant way, but we can add own handler for CTRL events. More than,
it fix another found ctrl+a bugs, which I saw during debug. E.g. I
couldn't select with ctrl+a after typing just "@jacob ".
elegant fix to unable editing inside of <span> with a smile.
@houd1ni houd1ni changed the title one approach to fix #258 one approach to fix #258 and elegant #262 May 12, 2015
@ichord
Copy link
Owner

ichord commented May 13, 2015

You rock! @houd1ni . I will check it later.

ichord added a commit that referenced this pull request May 17, 2015
one approach to fix #258 and elegant #262
@ichord ichord merged commit 0155309 into ichord:master May 17, 2015
@ichord
Copy link
Owner

ichord commented May 17, 2015

@houd1ni you can close issues via commit messages

fix #258 , fix #262

@ichord
Copy link
Owner

ichord commented May 17, 2015

oh..... I forgot that the element which has contenteditable=false can't be delete in firefox... It's a old problem.

@houd1ni
Copy link
Author

houd1ni commented May 18, 2015

Ooups, (Didn't test that issue properly -- my fail, soz) Will fix soon!
Thank you for the advice about commits!
By the way, demo in readme is still old, but It would be nice idea to update it after all fixes :)

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 this pull request may close these issues.

2 participants