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" attribute as the default presentation of a disabled text field.
Cheers Pedro Santos On Fri, Dec 2, 2016 at 7:07 AM, Dan Haywood <d...@haywood-associates.co.uk> wrote: > 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 possible on a lot of Chrome > installations of our users either, probably due to a Chrome update. This > really is a big problem for our users because we share a lot of > configuration data for internet access and telephony services and > copying data makes sure they don't make mistakes while configuring their > systems. > > Would it be a problem to use the read only attribute instead of the > disabled attribute? That would be an easy fix. > > > Martin G suggested a possible fix using CSS, but unfortunately to no > avail. Since this presumably could impact all Wicket users, the suggestion > [3] was to re-raise the question here. > > So, are there any thoughts on this? Is there any way to enable select text > for a disabled input field for both latest Chrome and Firefox? > > Thx > Dan > > [1] http://isis.apache.org/ > [2] > https://lists.apache.org/thread.html/354ff5bb35c3dd60fbe643f824951c > 9665aa7546d79562cf15e014f7@%3Cusers.isis.apache.org%3E > [3] > https://lists.apache.org/thread.html/566709f02cc6a4607d1f86d98e19ec > 1e7d39a2a255dc9895d5800635@%3Cusers.isis.apache.org%3E >
