You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When clicking between 2 instances of aloha which have been bound to different editable elements
there is no focus lost event triggered.
e.g
..
..
..
Steps to reproduce:
Aloha is bound to both foo and bar but not rar.
aloha(..query('#foo));
aloha(..query('#bar));
Click on any child of @id=foo then click on any child of @id=rar
an focus lost event is dispatched
Click on any child of @id=foo then click on any child of @id=bar
an focus lost event is not dispatched
Expected / Wish?:
when ever the focus has been lost from the element that is currently being edited it should send a signal of some sort
Why ?
You have multiple content editable parts of a web page. When you click on a content editable area, the section of the page currently being edited is highlighted to inform the user where they are editing. If they switch away it would be nice to automatically send the content to be saved and remove the highlighting. Currently we have to keep track of the focus manually by looking at the currentTarget of the event.
This seems like a reasonably common use case and would be nice to have upstream.
Kind regards
Andrew
The text was updated successfully, but these errors were encountered:
When clicking between 2 instances of aloha which have been bound to different editable elements
there is no focus lost event triggered.
e.g
Steps to reproduce:
aloha(..query('#foo));
aloha(..query('#bar));
an focus lost event is dispatched
an focus lost event is not dispatched
Expected / Wish?:
Why ?
You have multiple content editable parts of a web page. When you click on a content editable area, the section of the page currently being edited is highlighted to inform the user where they are editing. If they switch away it would be nice to automatically send the content to be saved and remove the highlighting. Currently we have to keep track of the focus manually by looking at the currentTarget of the event.
This seems like a reasonably common use case and would be nice to have upstream.
Kind regards
Andrew
The text was updated successfully, but these errors were encountered: