- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Oct 2012 21:51:17 +0000
- To: www-dom@w3.org
- Message-ID: <bug-19414-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19414 Priority: P2 Bug ID: 19414 CC: mike@w3.org, www-dom@w3.org Assignee: annevk@annevk.nl Summary: Implement finishPropagation() method QA Contact: public-webapps-bugzilla@w3.org Severity: major Classification: Unclassified OS: Windows XP Reporter: jab_creations@yahoo.com Hardware: PC Status: NEW Version: unspecified Component: DOM Product: WebAppsWG The DOM lacks the ability to finish executing events leaving authors having to guess if an event has finished executing or not. The need for the finishPropagation method can be summarized by the following Gecko bug here... https://bugzilla.mozilla.org/show_bug.cgi?id=768310 In short while working on a rich text editor I discovered that Gecko browsers copy the (X)HTML code of a page selection. In the absence of the ability to convert the selection to plain/text in older browsers I have the caret focused on an invisible textarea where after the event finishes the selection is automatically converted to plain/text. I then had to have JavaScript copy the text and place it where the user expected the text to be copied to. At best I had to use the setTimeout method under the presumption that x-number of milliseconds should be sufficient. By having the finishPropagation method I would instead be able to not guess if an event has finished firing. This would free authors from having to rely on setTimeout which should NOT have to be used so far out of context as work-arounds. It's very important that finishPropagation be implemented for ALL events both triggered by users and those artificially created through document.createEvent. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 9 October 2012 21:51:19 UTC