| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0002521 | NetSurf | Layout | public | 2017-02-07 12:16 | 2017-02-11 18:18 | ||||||||
| Reporter | Rik Griffin | ||||||||||||
| Assigned To | |||||||||||||
| Severity | minor | Reproducibility | always | ||||||||||
| Status | confirmed | Resolution | open | ||||||||||
| Platform | Iyonix | OS | RISC OS | OS Version | 5.22 | ||||||||
| Product Version | 3.7 | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0002521: Inputs with attributes "readonly" or "disabled" are rendered inconsitently | ||||||||||||
| Description | Inputs with type "text" are rendered greyed if they have the attribute "readonly" but not if they have the "disabled" attribute. Inputs with type "checkbox" are never greyed even if they have one or both of these attributes. The same applies to type "radio". For what it's worth, Chrome renders "disabled" inputs greyed out, whereas Firefox renders both "disabled" and "readonly" as greyed out. I don't think either of those browsers get it fully correct, as they both allows the user to change a "readonly" checkbox/radio. I think the correct behaviour would be for both "readonly" and "disabled" input items to be greyed and not editable by the user? | ||||||||||||
| Steps To Reproduce | Load attached file into Netsurf | ||||||||||||
| Additional Information | Version 3.7 build 3978 | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Fixed in CI build # | |||||||||||||
| Reported in CI build # | 3978 | ||||||||||||
| URL of problem page | |||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
Chris Young (developer) 2017-02-10 19:58 |
http://stackoverflow.com/questions/7730695/whats-the-difference-between-disabled-disabled-and-readonly-readonly-for-ht According to that, our textbox behaviour has the readonly/disabled visual greyed out effect the wrong way round. I can also gain focus on, and edit, the disabled textbox, which is incorrect. |
|
Chris Young (developer) 2017-02-11 17:31 |
CI build 3983 makes disabled textboxes non-editable. |
|
Chris Young (developer) 2017-02-11 18:18 |
I've also switched the visual indication over so that disabled textboxes get greyed out (and read-only ones don't). I believe behaviour of textboxes is correct now. Checkboxes and other form elements still need fixing to be uneditable and visually disabled. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-07 12:16 | Rik Griffin | New Issue | |
| 2017-02-07 12:16 | Rik Griffin | File Added: test.html | |
| 2017-02-10 19:58 | Chris Young | Note Added: 0001516 | |
| 2017-02-10 19:58 | Chris Young | Status | new => confirmed |
| 2017-02-10 19:58 | Chris Young | Category | RISC OS-specific => Layout |
| 2017-02-10 19:58 | Chris Young | Product Version | => 3.7 |
| 2017-02-11 17:31 | Chris Young | Note Added: 0001517 | |
| 2017-02-11 18:18 | Chris Young | Note Added: 0001518 | |
| Issue History |