Open Bug 1149076 Opened 7 years ago Updated 3 years ago
.target is not set correctly in content Editable
Attachment #8585362 - Attachment mime type: text/plain → text/html
I see the same behavior in other browsers too, and given the contenteditable element is the activeElement, key events should go there. Why you think this behavior is incorrect? Perhaps you want to use DOM0 UIEvent's rangeParent + rangeOffset properties?
Bulk priority change, per :mdaly
Priority: P3 → P5
This is BUG (not a feature) - in all browsers :( Test case: https://codepen.io/anon/pen/zmVRZL Reason? Why provide target click information is no problem, but provide proper target information for typing is problem? It should be similar (and similar) - but currently it is not trivial to get that information exactly on which element user type text :(
You need to log in before you can comment on or make changes to this bug.