On 12/09/2016 10:28 AM, Dan Haywood wrote:
just to say that I've raised ISIS-1552 [1] for this and it will be fixed in
1.13.2.
Thanks Dan!
Thx
Dan
[1] https://issues.apache.org/jira/browse/ISIS-1552
On Fri, 2 Dec 2016 at 09:08 Dan Haywood
wrote:
I've posted a question at us...@wicket.apa
just to say that I've raised ISIS-1552 [1] for this and it will be fixed in
1.13.2.
Thx
Dan
[1] https://issues.apache.org/jira/browse/ISIS-1552
On Fri, 2 Dec 2016 at 09:08 Dan Haywood
wrote:
> I've posted a question at us...@wicket.apache.org
>
>
> https://lists.apache.org/thread.html/f8c956cf
I've posted a question at us...@wicket.apache.org
https://lists.apache.org/thread.html/f8c956cff606d79c8a337fcf9b1b4de1e5dce71b793ebe59bdecfae7@%3Cusers.wicket.apache.org%3E
On Thu, 1 Dec 2016 at 21:28 Martin Grigorov wrote:
> On Thu, Dec 1, 2016 at 8:35 AM, Dan Haywood
> wrote:
>
> > It wou
On Thu, Dec 1, 2016 at 8:35 AM, Dan Haywood
wrote:
> It would seem this new behaviour in Chrome and also Firefox - probably
> making the browser more compliant with some specific - could cause issues
> for more many more Wicket apps than just Isis.
>
> Does Wicket have the notion of readonly inpu
It would seem this new behaviour in Chrome and also Firefox - probably
making the browser more compliant with some specific - could cause issues
for more many more Wicket apps than just Isis.
Does Wicket have the notion of readonly input elements rather than
disabled, that we could use instead?
I've played a bit with disabled input and indeed it is not possible to
select the text inside it.
Also http://getbootstrap.com/css/#forms-control-disabled (the first caveau)
says "disables all keyboard and mouse interactions".
Wicket sets "disabled" on FormComponents when they are "disabled in
hie
If Martin's suggestion of using CSS doesn't sort the issue, then I guess
the fix will need to be a little deeper perhaps using some other Wicket
API other than setDisabled(...). Maybe something like using an
AttributeModifier to put the "readOnly" attribute on instead, cf
http://stackoverflow.
On 11/30/2016 01:22 PM, Dan Haywood wrote:
oops. I meant https://issues.apache.org/jira/browse/ISIS-1547
Thanks Dan
On Wed, 30 Nov 2016 at 12:20 Dan Haywood
wrote:
Thanks both. I've created https://issues.apache.org/jira/browse/ISIS-1546
On Wed, 30 Nov 2016 at 11:35 Martin Grigorov
Hi Martin,
On 11/30/2016 12:34 PM, Martin Grigorov wrote:
Hi,
I guess the "disabled" attribute comes from Wicket.
If a FormComponent is setEnabled(false) then Wicket will set this attribute
to the HTML form element (input. textarea, etc.).
IMO the correct solution is to override the CSS rule th
oops. I meant https://issues.apache.org/jira/browse/ISIS-1547
On Wed, 30 Nov 2016 at 12:20 Dan Haywood
wrote:
> Thanks both. I've created https://issues.apache.org/jira/browse/ISIS-1546
>
>
> On Wed, 30 Nov 2016 at 11:35 Martin Grigorov wrote:
>
> Hi,
>
> I guess the "disabled" attribute com
Thanks both. I've created https://issues.apache.org/jira/browse/ISIS-1546
On Wed, 30 Nov 2016 at 11:35 Martin Grigorov wrote:
> Hi,
>
> I guess the "disabled" attribute comes from Wicket.
> If a FormComponent is setEnabled(false) then Wicket will set this attribute
> to the HTML form element (i
Hi,
I guess the "disabled" attribute comes from Wicket.
If a FormComponent is setEnabled(false) then Wicket will set this attribute
to the HTML form element (input. textarea, etc.).
IMO the correct solution is to override the CSS rule that disables the
selection of the text.
Play with
-webkit-us
If you are certain that using 'readonly' would do the trick, then please
raise a ticket for that.
Thx
On Wed, 30 Nov 2016 at 09:44 Erik de Hair wrote:
> Hi,
>
> I believe it was mentioned once in another thread that selecting text
> (and so copying) from a disabled field doesn't work in Firefox
13 matches
Mail list logo
