Open
Bug 1133804
Opened 10 years ago
Updated 3 years ago
Click on `<textarea readonly ...>...` element => cursor shows up but should not.
Categories
(Core :: Layout: Form Controls, defect)
Core
Layout: Form Controls
Tracking
()
UNCONFIRMED
People
(Reporter: frohring.pierrehenry, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
7.62 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150122214805
Steps to reproduce:
I have this element in my HTML page:
<textarea style="overflow: hidden; word-wrap: break-word; height: 19px;" readonly="" placeholder="No title yet" class="expand activated"></textarea>
I clicked on it...
Actual results:
... the cursor shows up in the textarea ...
Expected results:
... but should not because it's readonly. => false indication to the user that it's not readonly when it's readonly.
Reporter | ||
Updated•10 years ago
|
Summary: Click on `<textarea readonly ...>...` element => cursor shows up but not in chrome. → Click on `<textarea readonly ...>...` element => cursor shows up but should not.
Comment 1•10 years ago
|
||
I think we show the caret intentionally to enable keyboard navigation and selection.
The indication that it's readonly is the grey background.
Testcase: data:text/html,<textarea readonly="">some text</textarea>
Severity: normal → minor
Component: DOM: Core & HTML → Layout: Form Controls
Keywords: testcase
OS: Mac OS X → All
Hardware: x86 → All
Version: 35 Branch → unspecified
Reporter | ||
Comment 2•10 years ago
|
||
Well... I tested it on a few people (nbr not exactly significant (< 10) but anyway...):
- Here is the behaviour of Chrome, (readonly => which means no caret)
- Here is the behaviour of Firefox, (readonly => which means caret)
- What do you expect when you click here ?
=> no caret
Interpretation:
- caret present =>
expectation: next time "I" type on the keyboard, it will move forward leaving behind the character I typed in
=> So, where a caret is present should be a mutable element.
- if readonly then element should not be mutable
=> caret should not be present
=> I don't expect from typing on the keyboard for the element to be modified.
Thx for looking at it...
Updated•3 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•