I discovered something very dangerous:
In non-editable date fields you can still edit the day, month and year by just selecting it and use the arrow-up and -down keys.
How can we avoid this?
TIA
Stef
I discovered something very dangerous:
In non-editable date fields you can still edit the day, month and year by just selecting it and use the arrow-up and -down keys.
How can we avoid this?
TIA
Stef
Stef:
I discovered something very dangerous:In non-editable date fields you can still edit the day, month and year by just selecting it and use the arrow-up and -down keys.
How can we avoid this?
TIA
Stef
Formatting them as text field won’t allow that. But I’m not sure it’s what you want…
What do you mean, Riccardino?
Display type = text field?
TIA
Stef
I made a presentation to make it clear:
Stef:
What do you mean, Riccardino?Display type = text field?
TIA
Stef
Ah, wait: now I see what you mean.
Entering the field, you can’t select anything BUT double-clicking on the part of the date will allow changes even if the field is non-editable.
Hmmm: this is an unexpected behaviour, I’m afraid.
Until we have an official answer, you could consider using:
elements.your_date_field.enabled = false
But you could have unwanted side-effects…
Hope it helps
Ciao
Thanks, Ricardo!
This helps, but now I need a couple of hours to make this safe everywhere… (make elements, onload method,…)
Unless the dev team finds a solution???
TIA!
Stef
I’ve found something similar.
When you have an non-editable text field and have the text toolbar enabled you still can set the styles, etc. of the text.
This is highly undesirable!
Non-editable fields should be just that. Not somewhat non-editable.
Just to confirm.
I have a simular issue regarding showing dates in a non editable textbox.
Kind regards Rene
fixed this for 3.0
I will try to backport it to a 2.2.x release