Improve design of form fields (MGNLUI-1610)

[MGNLUI-1088] Combo-boxes should not be editable by default Created: 11/Apr/13  Updated: 05/Jun/15  Resolved: 11/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Sub-task Priority: Blocker
Reporter: Andreas Weder Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: acceptance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

magnolia-bundle_stable build #35 (2013-04-08 14:27:35)


Attachments: PNG File Bildschirmfoto 2013-06-10 um 18.01.20.png     PNG File bonfire-screenshot-20130411-114043-941.png    
Issue Links:
relation
is related to MGNLUI-3438 filterMode on Select-Fields has no ef... Closed
Template:
Date of First Response:

 Description   

Combo boxes currently are all editable. Why they could potentially be editable for fields supporting that (e.g. for tags), they shouldn't be by default.



 Comments   
Comment by Mikaël Geljić [ 10/Jun/13 ]

Seems to be already the case.

Comment by Andreas Weder [ 10/Jun/13 ]

I'm re-opening this because this seems not to be entirely solved.

It is correct that combo boxes are not editable by default, but a cursor does show up, when you click into them. Observed on Firefox 21.0 on OS X. Not observed on Safari 6.0.4.

Comment by Mikaël Geljić [ 11/Jun/13 ]

The cursor at the end of the field is indeed due to the underlying text input which is readonly when the ComboBox is non-editable. It is actually an accessibility feature that you can still select readonly text with the keyboard; Chrome and Safari are currently ignoring that.

On the other hand, it would be down to the Vaadin ComboBox to use something else than the text input when it's non-editable.

Generated at Mon Feb 12 08:43:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.