Backspace key weird results

[kleky]

Re: Backspace key weird results

Here is the code as I have followed it's progression...

//========================================
// Disable Backspace key in IE and Firefox
//========================================
// Trap Backspace(8) and Enter(13) - 
// Except bksp on text/textareas, enter on textarea/submit

document.onkeypress = function(event) {
if (typeof window.event != 'undefined') { // ie
event = window.event;
event.target = event.srcElement; // make ie confirm to standards !!
}
var kc=event.keyCode;
var tt=event.target.type;
if ((kc == 13) && (event.target.getAttribute('enter_ok') == 'true')) {
return true; // ok
}

// alert('kc='+kc+", tt="+tt);
if ((kc != 8 && kc != 13) || ((tt == 'text' || tt == 'password') && kc != 13) ||
(tt == 'textarea') || (tt == 'submit' && kc == 13))
return true;
alert('Bksp/Enter is not allowed here'); 
return false;
}

if (typeof window.event != 'undefined') // ie
document.onkeydown = document.onkeypress; // Trap bksp in ie. !! Note: does not trap enter, but onkeypress does !!

Place this in the ClientSide, OnGridRender event. Works great!

Charlie

Many many thanks...this works a treat!! problem solved. Surley J.R. has tried this?

As Charlie said, place in grid client-side OnGridRender, or for Dialogs, client-side OnRenderComplete.

[kleky]

Re: Backspace key weird results

This issue also occurs with dropdowns, so editable text boxes are the least of your concerns.

[2ninerniner2]

Re: Backspace key weird results

You didn't mention if this was in a Dialog or a Grid, but for me, in a Grid, all I do is set the fields I want as read-only to a Label Control type and adjust the Label Properties > In-line style as required.

For example, in the screenshot, the Employee Detail > Login is set to:

color: #ffffff; background-color: #008000; border-color: #33cc33; padding-bottom: 2px; padding-left: 5px; padding-right: 100px; padding-top: 2px;

This is from IE9 on Win 7 ... not dimmed at all


read-only_field.jpg

[agillbb]

Re: Backspace key weird results

My preferred way is to leave the field editable, but hide it!
Then use a dummy static field to display the value.
Use simple js statements to set the field's value - trigger it via a js event or otherwise.
You are really only using this dummy field's DIV to display your data.
You can also make it bold and red if you like.

[J.R. Noe]

Re: Backspace key weird results

the field is set up to receive a barcode number, and once entered it must remain unchanged, so i set it to read only once there is a value in it. But it still needs to be able to be seen and referenced and if t is not enabled, it is too dim to be very readable. That is why it is set up that way, but if someone has a better idea then please let me know. Everyone made very good points about not allowing the curser to even enter the field, so i thought i had better explain. Thanks everyone.

Maybe i should have it setup to pop up a message box saying "the field cannot be edited" and then set the focus to another field once the messagebox is closed.

[frankbicknell]

Re: Backspace key weird results

Again, why should a user be able to place their cursor where it's not supposed to do anything? :) IMHO, this is a UI/UX issue; a read-only field should be differentiated from one that is editable. To do otherwise leads to this discussion

I agree totally.

The problem I had with IE is that if you disable the field the text is 'dimmed' and is almost unreadable. I found out that that is controlled by the browser and can't be changed. I tried many different ways to solve this issue but nothing really worked. Now I use Firefox and the disabled fields text is not dimmed. I show that it is not an editable field by changing the backcolor. De-selecting the Updatable property works most of the time but allows users to see lists from lookups.

[Charles Hoens]

Re: Backspace key weird results

Yes, Neo, we are in the Matrix!

[2ninerniner2]

Re: Backspace key weird results

Again, why should a user be able to place their cursor where it's not supposed to do anything? :) IMHO, this is a UI/UX issue; a read-only field should be differentiated from one that is editable. To do otherwise leads to this discussion

[Charles Hoens]

Re: Backspace key weird results

Just because a field is read only doesn't mean that a user can't put their cursor there and then try and "back-up". That's what my users were doing and what took them out of the page.

[2ninerniner2]

Re: Backspace key weird results

Just out of curiosity, how is it that a read-only field is able to be entered?

If it is read-only, then why have it "enter-able"? As a user, this behavior would confuse me.

[Charles Hoens]

Re: Backspace key weird results

Here is the code as I have followed it's progression...

//========================================
// Disable Backspace key in IE and Firefox
//========================================
// Trap Backspace(8) and Enter(13) - 
// Except bksp on text/textareas, enter on textarea/submit

document.onkeypress = function(event) {
if (typeof window.event != 'undefined') { // ie
event = window.event;
event.target = event.srcElement; // make ie confirm to standards !!
}
var kc=event.keyCode;
var tt=event.target.type;
if ((kc == 13) && (event.target.getAttribute('enter_ok') == 'true')) {
return true; // ok
}

// alert('kc='+kc+", tt="+tt);
if ((kc != 8 && kc != 13) || ((tt == 'text' || tt == 'password') && kc != 13) ||
(tt == 'textarea') || (tt == 'submit' && kc == 13))
return true;
alert('Bksp/Enter is not allowed here'); 
return false;
}

if (typeof window.event != 'undefined') // ie
document.onkeydown = document.onkeypress; // Trap bksp in ie. !! Note: does not trap enter, but onkeypress does !!

Place this in the ClientSide, OnGridRender event. Works great!

Charlie

[agillbb]

Re: Backspace key weird results

Yea, apparently its a common problem.
http://mspeight.blogspot.com/2007/05...in-ie-and.html

[kkfin]

Re: Backspace key weird results

Backspace is Back and Shift + Backspace is Forward

Here is a list of shortcuts I have bookmarked (old but still valid )

[J.R. Noe]

Re: Backspace key weird results

Thanks Jeff, it may be normal, but it is not desireable in a web based application. I get complaints on it on a regular basis, and i agree with the complaints, it should not do that. Filling out a form in my application, it is just habit to hit the backspace key, which then kicks you off the page, causing much frustration. capturing the backspace key would seem to work, but i think it will just cause problems for data entry.
i have checked other web based applications and the backspace key works as needed, so i know it can be done.

[marvinbase]

Re: Backspace key weird results

Isn't this just normal browser behavior? From here, go to almost any other web page and click anywhere that isn't a form field. When I press backspace, it takes me back to the prior page in IE. (Note- doesn't work with google.com but does with news.google.com- perhaps they capture the backspace keystroke in javascript??)