On 11/07/2016 03:06 PM, Dan Haywood wrote:
Perhaps you could just throw and catch a stacktrace in both cases, logging
to stdout; then force the error and see what you get?
I'm sorry. I can't figure this out. May be it's gone with the next
Wicket upgrade. It's not really a problem because the u
Yes, do raise a ticket for the double-click issue; I think Martin suggested
that it would be fixable.
Thx
On Wed, 30 Nov 2016 at 08:07 Erik de Hair wrote:
>
> On 11/07/2016 03:06 PM, Dan Haywood wrote:
> > Perhaps you could just throw and catch a stacktrace in both cases,
> logging
> > to stdou
Created ticket https://issues.apache.org/jira/browse/ISIS-1544
On 11/30/2016 09:09 AM, Dan Haywood wrote:
Yes, do raise a ticket for the double-click issue; I think Martin suggested
that it would be fixable.
Thx
On Wed, 30 Nov 2016 at 08:07 Erik de Hair wrote:
On 11/07/2016 03:06 PM, Dan Ha
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 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 bi
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
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
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
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
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
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
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.
Ahah, column 'target' can be null in the mean time (I believe this
wasn't the case a while ago?). I just have to change the nullable
property in the database... It is explicitly set to null for view models.
On 11/30/2016 04:23 PM, Erik de Hair wrote:
Hi,
I'm getting following error when our
Hi,
I'm getting following error when our application is trying to persist a
command (finish() action on view model
nl.pocos.dom.access.kpn.wba.order.WbaFiberOrderForm).It is not
neccessary to persist the command so I tried so suppress that by adding:
@Action(commandPersistence = CommandPersi
Dear Apache enthusiast,
ApacheCon and Apache Big Data will be held at the Intercontinental in
Miami, Florida, May 16-18, 2017. Submit your talks, and register, at
http://apachecon.com/ Talks aimed at the Big Data section of the event
should go to
http://events.linuxfoundation.org/events/apache-bi
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
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?
16 matches
Mail list logo
