NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: Keith on April 02, 2014, 11:53:09 AM

Title: Bypassing Read-Only fields
Post by: Keith on April 02, 2014, 11:53:09 AM

Hi

On a Form is there a way to make the 'Tab' key skip the Read-Only fields?

Keith

Title: Re: Bypassing Read-Only fields
Post by: debzidoodle on April 02, 2014, 03:25:06 PM

I use the following javascript to skip a delete button in an edit in place browse.  Maybe it will do what you need

Code: [Select]

btnDeletes = document.getElementsByName("deleteb_btn");

for(var x=0; x < btnDeletes.length; x++) 
{
    btnDeletes[x].setAttribute("tabindex",-x);
}

Title: Re: Bypassing Read-Only fields
Post by: terryd on April 03, 2014, 01:56:14 AM

Hi Keith
How about setting the fields as display fields.

Title: Re: Bypassing Read-Only fields
Post by: Keith on April 04, 2014, 12:13:53 PM

Hi Terry

Setting to Display works in that the field is bypassed but there are bad side-effects  >:(

The styling is omitted and the 'right-justify' is ignored.  But its worth remembering.

Thanks

Keith

Title: Re: Bypassing Read-Only fields
Post by: Bruce on April 07, 2014, 12:29:50 AM

You can obviously add the css effects you want to the display field.

It would take a bit of JavaScript to make it ship over read-only fields when tabbing though. Using the Display type, with the correct css, is the best approach I think.

cheers
Bruce

Title: Re: Bypassing Read-Only fields
Post by: Keith on April 09, 2014, 01:41:25 PM

Thanks everyone

I agree that creating the Display style that is appropriate would be worth doing.

Cheers

Keith

Title: Re: Bypassing Read-Only fields
Post by: Keith on April 15, 2014, 02:14:20 AM

Hi  all

I can report that I now have a style (my-readonly) that makes a display field look like a standard read-only field but which causes 'tabs' and 'returns' to bypass them.  Thanks for the advice on this and I must say again that this is a brilliant result.

Have a look at the 'Read-only' image.  The user could change some of the fields in the first three columns but after 'tab' the cursor could move into the read-only fields in the last four columns.  This was annoying and begged the question - 'if you're not supposed to change these values then why allow the cursor to go there?'

The new style renders only the first three columns active and is a great result - the cursor obediently goes only to the fields that can be changed.

I will post the css on the 'Share' section so that others can use it if it has value.

Cheers

Keith

[attachment deleted by admin]