Eclipse Community Forums: Remote Application Platform (RAP) » Backspace in non editable textfield triggers browser action

Home » Eclipse Projects » Remote Application Platform (RAP) » Backspace in non editable textfield triggers browser action

Show: Today's Messages :: Show Polls :: Message Navigator

Backspace in non editable textfield triggers browser action [message #820552]

Wed, 14 March 2012 05:11

Sabine Neubauer
Messages: 15
Registered: June 2011

Junior Member

Hi,

in our application (based on RAP 1.4) there are several text fields which are enabled but not editable. In this way we provide the possiblity to mark the content of these fields in order to copy it.

If a non editable text field is focused and an user presses "backspace" the browser jumps back to the former shown side (default browser action). This behavior is not really intuitive and has changed since RAP 1.1. I found the bugzilla issue 178320 ([Key-Events] Disable browser key shortcuts like Backspace in RAP) concerning this "problem" which was fixed for RAP 1.1.1

Is the current behavior desired or is this a regression/bug?

I have already tested RAP 1.5 M5 but the behavior is the same as in 1.4. Using RWT.CANCEL_KEYS is not sufficient in our use case, because the editable state depends on a certain selection and if it changes a little gap where the key event leads to the browser action seems to exist.

Kind regards
Sabine

Report message to a moderator

Re: Backspace in non editable textfield triggers browser action [message #820586 is a reply to message #820552]

Wed, 14 March 2012 05:59

Tim Buschtoens
Messages: 246
Registered: July 2009

Senior Member

Hi.

> Is the current behavior desired or is this a regression/bug?

If it worked before, i would consider it a bug. Usually, browser
shortcuts are only automatically prevented/overwritten if the focused
widget associates an action with that key. In case of a non-editable
Text field there is no action for backspace, but its still the same
widget and also looks the same, so i think the rule applies.

Please open a new bug for this instead of re-opening the old one. It
should be fixed for 1.5 then.

> Using RWT.CANCEL_KEYS is not sufficient in our use case, because the
> editable state depends on a certain selection and if it changes a little
> gap where the key event leads to the browser action seems to exist.

I'm not sure i fully understand that. If you set the CANCEL_KEYS
together with the editable property (same request), its still possible
to trigger the history-back action?

Greetings,
Tim

--
Tim Buschtöns

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/

Report message to a moderator

Re: Backspace in non editable textfield triggers browser action [message #820614 is a reply to message #820586]

Wed, 14 March 2012 06:43

Sabine Neubauer
Messages: 15
Registered: June 2011

Junior Member

Hi Tim,

thanks for your reply. I open a new bug (issue 374192).

Quote:

> Using RWT.CANCEL_KEYS is not sufficient in our use case, because the
> editable state depends on a certain selection and if it changes a little
> gap where the key event leads to the browser action seems to exist.

I'm not sure i fully understand that. If you set the CANCEL_KEYS
together with the editable property (same request), its still possible
to trigger the history-back action?

I have a further look at this problem. Dependent on the used browser I have two different problems:
- using IE 8: pressing the backspace key twice in a short interval triggers the history-back action
- using FF: the history-back action is only triggered because the textfield (part of a view) loses the focus after I have clicked on it the first time, but if the focus is not lost (clicked a further time) the history-back action is *not* triggered

I think the IE "problem" can be a general one. The FF "problem" is probably located in our own application, but I will make further investigations as soon as possible.

Kind regards
Sabine

Report message to a moderator

Re: Backspace in non editable textfield triggers browser action [message #820617 is a reply to message #820586]

Wed, 14 March 2012 06:43

Sabine Neubauer
Messages: 15
Registered: June 2011

Junior Member

Hi Tim,

thanks for your reply. I open a new bug (issue 374192).

Quote:
> > Using RWT.CANCEL_KEYS is not sufficient in our use case, because the
> > editable state depends on a certain selection and if it changes a little
> > gap where the key event leads to the browser action seems to exist.
>
> I'm not sure i fully understand that. If you set the CANCEL_KEYS
> together with the editable property (same request), its still possible
> to trigger the history-back action?

I have a further look at this problem. Dependent on the used browser I have two different problems:
- using IE 8: pressing the backspace key twice in a short interval triggers the history-back action
- using FF: the history-back action is only triggered because the textfield (part of a view) loses the focus after I have clicked on it the first time, but if the focus is not lost (clicked a further time) the history-back action is *not* triggered

I think the IE "problem" can be a general one. The FF "problem" is probably located in our own application, but I will make further investigations as soon as possible.

Kind regards
Sabine

Report message to a moderator

Previous Topic:	Backspace in non editable textfield triggers browser action
Next Topic:	RAP Theme dynamic

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed May 22 16:15:42 EDT 2013