Make the <summary> element not selectable by default
Reported by
xfq.f...@gmail.com,
Nov 2 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:56.0) Gecko/20100101 Firefox/56.0 Example URL: https://jsfiddle.net/936vkxn4/ Steps to reproduce the problem: 1. Create a <details> element, containing one <summary> element followed by flow content. 2. Click the <summary> element quickly for several times What is the expected behavior? The text in the <summary> element should not be selected. What went wrong? The text in the <summary> element is selected. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? No Firefox 56 and Safari 11, at least Chrome version: 61.0.3163.100 (Official Build) (64-bit) Channel: stable OS Version: OS X 10.13 Flash Version: 27.0.0.183 /Users/xfq/Library/Application Support/Google/Chrome/PepperFlash/27.0.0.183/PepperFlashPlayer.plugin When expanding/collapsing the <details> element, it's really easy to select the text in the <summary> element accidentally when expanding and collapsing a section quickly (just for a quick short look at the section, for example), which is annoying. Personally, I'd really like to disable the selection of the <summary> element by default, but I'm also glad to hear other people's comments on this suggestion.
,
Nov 2 2017
,
Nov 3 2017
I filed a spec issue here: https://github.com/whatwg/html/issues/3191
,
Nov 3 2017
Able to reproduce this issue on reported verison 62.0.3202.75 and on latest canary 64.0.3256.0 using Windows 10,Ubuntu 14.04 and Mac 10.12.6 with steps mentioned in comment#0. This issue is seen from M50[50.0.2661.0]. Hence considering this as Non-regression and marking this as Untriaged
,
Dec 6 2017
,
Dec 6
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 10
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by woxxom@gmail.com
, Nov 2 2017I agree it's weird and counter-intuitive, but apparently the specification doesn't define it explicitly. You can modify the behavior via CSS: summary { user-select: none; cursor: pointer; }