Bug 90679 - <details> doesn't fire selectstart
Summary: <details> doesn't fire selectstart
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://jsfiddle.net/hgXsG/
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-06 05:57 PDT by pimvdb
Modified: 2022-12-07 14:25 PST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pimvdb 2012-07-06 05:57:10 PDT 
Adding a selectstart listener to the body element that does e.preventDefault() should prevent anything from being selected. However, when the selection starts in a <details> element (or any of its descendants), the event is not fired.

Test case: http://jsfiddle.net/hgXsG/

Dragging "baz" is not possible because the selectstart event is fired correctly (it's not a descendant of a <details> element). A confirmation is also logged in the console. However, one *is* able to select "foo", "bar" and "hello", which are all in the <details> element. The event is not fired at all; nothing is logged to the console.

It does not happen on Google Chrome 20, but it does happen on Google Chrome 22.
Comment 1 pimvdb 2012-07-21 08:13:13 PDT 
This seems to have been fixed as I cannot reproduce anymore.
Comment 2 Lucas Forschler 2019-02-06 09:19:15 PST 
Mass move bugs into the DOM component.
Comment 3 Ahmad Saleem 2022-12-07 14:25:56 PST 
I am not able to reproduce this in Safari 16.1 and "selectstart" event do log in console.

Marking this as "RESOLVED CONFIGURATION CHANGED". Thanks!