The Apache Isis project [1] uses Wicket for its main viewer, and we
recently had this question [2] on our mailing list is:
I believe it was mentioned once in another thread that selecting text
(and so copying) from a disabled field doesn't work in Firefox on
Windows. Since a week or two it's not p
Hi,
too bad the Firefox developers can't read a spec correctly :P
https://www.w3.org/TR/2014/REC-html5-20141028/forms.html#the-readonly-attribute
"The difference between disabled and readonly is that read-only controls
are still focusable, so the user can still select the text and interact
wit
After reading the thread on Isis's mailing list, I'm under the impression
that the best solution is to offer an API enabling users to configure how
the disabled text field will be shown. My suggestion is to add the method
TextField.showDisabledAsReadOnly(boolean) and to keep the current
"disabled"
I just remembered that we utilized this trick back when IE 6? used to render
disabled text inputs with unreadable colors.
Sven
Am 2. Dez. 2016, 12:19, um 12:19, Sven Meier schrieb:
>Hi,
>
>too bad the Firefox developers can't read a spec correctly :P
>
>https://www.w3.org/TR/2014/REC-html5-20
Hello,
I'm trying to change PagingNavigation: current page of navigation is a
not-clickable number by default. I'd like to have textbox instead.
Straightforward solution seems to be overriding method populateItem(LoopItem
loopItem) from PagingNavigation class.
But so far I have not figured out
On Fri, Dec 2, 2016 at 12:21 PM, Pedro Santos wrote:
> After reading the thread on Isis's mailing list, I'm under the impression
> that the best solution is to offer an API enabling users to configure how
> the disabled text field will be shown. My suggestion is to add the method
> TextField.showD
