Right now, the read-only field (a) changes appearance when focused, (b)
to white, (c) is debossed, and (d) has a blinking insertion point.
Combined with the fact that its label isn't greyed out, those four clues
strongly indicate that I can type into it. The only thing that prevented
me from thinking that the OSK not appearing here was a bug was the fact
that that I happened to design this screen myself.

That's why I didn't say a read-only text field should always look
focused; that wouldn't solve the problem at all. I said it should look
exactly the same when it isn't focused as when it is.

In most toolkits, read-only text fields (a) aren't even focusable, (b) or if 
they are, they don't change color, (c) they have flatter edges than read-write 
fields, and (d) they don't have an insertion point (except for accessibility 
purposes when you can't select text with a pointing device). You can see how 
your browser renders the difference, for example, by copying and pasting the 
following line into the address field:
data:text/html,<input><input disabled>

(Unfortunately data: URIs don't work with the Ubuntu Browser; I've just
reported that as bug 1377953.)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370571

Title:
  Read-only text field doesn't look read-only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1370571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to