problem with form buttons

[Michael Chernecki]

Hi,
Not sure if I am posting to the proper group. I have some buttons on an
HTML form. When I click a button, it just gives the button focus. Then I
need to click again for the onClick actions to take place. How do I get
the buttons to work on the fist clck, rather two clicks or a double click.
I have set tab order and have used xxx.focus() to give the first field on
the form fucus after the form loads. Can this be screwing the buttons up.
Any help would be appreciated.

Thanks
Mike

[Jukka K. Korpela]

Re: problem with form buttons

mchernecki@yaho o.com (Michael Chernecki) wrote:
[color=blue]
> Not sure if I am posting to the proper group.[/color]

You probably aren't, if you are not sure. It would be more useful to
spend some time in finding the right group, while trying to analyze what
your problem really is.
[color=blue]
> I have some buttons on
> an HTML form. When I click a button, it just gives the button focus.[/color]

You didn't specify a URL, or the browser(s) tested.
[color=blue]
> I have set tab order and have used xxx.focus() to give
> the first field on the form fucus after the form loads.[/color]

If you need to set tab order, the page structure is probably wrongly
designed.

Setting focus in JavaScript is known to cause various problems. The
details depend on _how_ you do that.

--
Yucca, http://www.cs.tut.fi/~jkorpela/
Pages about Web authoring: http://www.cs.tut.fi/~jkorpela/www.html

[J. Clancey]

Re: problem with form buttons

Did you put in an action page for the form? Display the code for the submit button.

Later,
J.Clancey

[DKrapohl]

Re: problem with form buttons

If you are using a Microsoft debugger and IE, go (in IE) to view,
script
debugger, break at next statement. Then click your button. It will
fire some event that will be caught in the debugger. If you don't see
'script debugger' under the IE view menu, go to tools, internet
options, advanced, and then de-select the 'disable script debugging'
option if it is checked. You'll have to close all your browsers for
this to take effect.

Don Krapohl

http://www.tranquillitas.com

Website quality assurance testing


john_clancey@tj x.com (J. Clancey) wrote in message news:<bc9fd422. 0308260741.2aea 16ed@posting.go ogle.com>...[color=blue]
> Did you put in an action page for the form? Display the code for the submit button.
>
> Later,
> J.Clancey[/color]

[Michael Chernecki]

Re: problem with form buttons

In article <74293823.03082 71707.48917bdd@ posting.google. com>,
dkrapohl@tranqu illitas.com (DKrapohl) wrote:
[color=blue]
> If you are using a Microsoft debugger and IE, go (in IE) to view,
> script
> debugger, break at next statement. Then click your button. It will
> fire some event that will be caught in the debugger. If you don't see
> 'script debugger' under the IE view menu, go to tools, internet
> options, advanced, and then de-select the 'disable script debugging'
> option if it is checked. You'll have to close all your browsers for
> this to take effect.
>
> Don Krapohl
> http://www.tranquillitas.com
> Website quality assurance testing
>
>
> john_clancey@tj x.com (J. Clancey) wrote in message[/color]
news:<bc9fd422. 0308260741.2aea 16ed@posting.go ogle.com>...[color=blue][color=green]
> > Did you put in an action page for the form? Display the code for the[/color][/color]
submit button.[color=blue][color=green]
> >
> > Later,
> > J.Clancey[/color][/color]

Don, Thnaks for the information. I have tried to get the debugger working
on my computer, but still no luck. I did get it working on another
computer and narrowed the problem down to a statement using .focus(), it
works ok now.

Thanks
Mike

[Mr. Zucchini]

Re: problem with form buttons

On Thu, 28 Aug 2003 10:32:15 -0400, DKrapohl wrote
(in message <74293823.03082 80632.7f085322@ posting.google. com>):
[color=blue]
> The site has been tested with numerous tools and we are aware that
> there are a few issues, some inherent to our choice of technology.
> This does not detract from our mission. Our focus is to note issues
> with a website and hand the report to developers to repair.
>
> Any suggestions on/for the site?[/color]

Yeah.

- Make sure that your site at least has valid markup.
- Random contents are a bad idea.
- useless content is a bad idea. I tried to get to the 'browser test'
thingy and had to reload the page six time to get to one with a
functioning link, I got it three times with no link, just the words
'Browser Test'.
- static content size that is larger than smaller windows is a bad idea.
- heavy use of javascript is a bad idea.
- Some of your contents are old and outdated.
- It's a bad sign when one accesses a report on broken links on your
site and the report contains broken links.
Check this page on your site:

http://www.tranquillitas.com/resources/qtart.htm

and check the link at the bottom of the page.

Your website is sooo 1998.

I do the quality assurance of my own sites, but let's say somebody ever
asks me about a service like yours, I would definitely not point them
your way, based on what I saw on your site. For the services that you're
offering, your website is your resume. If you were offering services
that had nothing to do with web design or site maintenance then I
wouldn't have commented, but you do...

[Stephen Poley]

Re: problem with form buttons

On 28 Aug 2003 07:32:15 -0700, dkrapohl@tranqu illitas.com (DKrapohl)
wrote:
[color=blue]
>The site has been tested with numerous tools and we are aware that
>there are a few issues, some inherent to our choice of technology.
>This does not detract from our mission. Our focus is to note issues
>with a website and hand the report to developers to repair.
>
>Any suggestions on/for the site?[/color]

The most obvious one is to use the reader's font size for the main text
on each page, in order to ensure that the page is legible. See

http://www.xs4all.nl/~sbpoley/webmatters/fontsize.html

[color=blue]
>Thank you for your question.
>
>
>Don Krapohl
>http://www.tranquillitas.com
>Website quality assurance testing[/color]

--
Stephen Poley

http://www.xs4all.nl/~sbpoley/webmatters/