Bugzilla

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(PTO: 5/2-5/10) from comment #2)
> Be careful about the editable case. Chrome allows to select and edit the text in `<button>`.

Thanks, good callout.  Specifically for <button>, Chrome does indeed let you click-and-drag-within-the-button to select text, but only if your initial click is in the text part of the button (as opposed to the padding).

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(PTO: 5/2-5/10) from comment #2)
> Be careful about the editable case. Chrome allows to select and edit the text in `<button>`.

Thanks, good callout.  In `contenteditable`, specifically for <button>, Chrome does indeed let you click-and-drag-within-the-button to select text, but only if your initial click is in the text part of the button (as opposed to the padding).

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(PTO: 5/2-5/10) from comment #2)
> Be careful about the editable case. Chrome allows to select and edit the text in `<button>`.

Thanks, good callout.  In `contenteditable`, specifically for <button>, Chrome does indeed let you click-and-drag-within-the-button to select text, but only if your initial click is in the text part of the button (as opposed to the padding).

That seems to match how Firefox currently behaves for `<input type="button">` (regardless of contenteditable), actually!

For true `<button>` (first part of testcase 1 and testcase 2), Firefox lets you click the padding-top and drag down to the padding-bottom, and select all the text in between.

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(PTO: 5/2-5/10) from comment #2)
> Be careful about the editable case. Chrome allows to select and edit the text in `<button>`.

Thanks, good callout.  In `contenteditable`, specifically for <button> (first part of testcase 2), Chrome does indeed let you click-and-drag-within-the-button to select text, but only if your initial click is in the text part of the button (as opposed to the padding).

That seems to match how Firefox currently behaves for `<input type="button">` (regardless of contenteditable), actually!

For true `<button>` (first part of testcase 1 and testcase 2), Firefox lets you click the padding-top and drag down to the padding-bottom, and select all the text in between.