339395 - Readonly textboxes and inputs shouldn't look active

Status: RESOLVED FIXED

(Core :: Widget: Gtk, defect)

Description

[Phil Ringnalda (:philor)]

Gtk version of bug 339192 - <input readonly> in HTML really shouldn't look just like an active input, and Firefox (in bug 337344) and Thunderbird (in bug 297815) both need to have <textbox readonly="true"> not look like an active textbox that's broken, because you can't type in it for some buggy reason. Disabled background but active text seems like a reasonable appearance.

HTML testcase in attachment 223267 [details] and XUL testcase in 223268 (but unfortunately nsNativeThemeGTK.cpp isn't close enough to just port the patch, and in fact seems to ignore what I tell it about the disabled state of readonly textboxes).

Comment 1

[Greg K.]

This is a problem across all platforms and products (for example, Camino on Mac in my case, and also Firefox 1.5).

Moreover, on trunk (Camino/1.2+ and GranParadiso 3.0a1) readonly inputs also show a nonblinking I-beam cursor when focused, which is even more misleading.

See testcase attachment 147140 [details] on bug 143520.

Reassigning to Layout: Form Controls and setting All/All.

Comment 2

[Greg K.]

Bug 143520 may also be relevant.

Comment 3

[Phil Ringnalda (:philor)]

Putting back where it belongs: please do actually read comment 0 before moving bugs around. You see it in Firefox 1.5 on Mac because I fixed it for Mac after 1.5 shipped. If you see a bug which is not "readonly textboxes on Linux have the same appearance as non-readonly textboxes" then it is not this bug, and you'll want to file another one.

Comment 4

[Greg K.]

(In reply to comment #3)
> Putting back where it belongs: please do actually read comment 0 before moving
> bugs around. 

Sorry about that, Phil. I don't know where my mind was.

Comment 5

[Michael Ventnor]

Fixed as part of the patch in bug 329846.