how to keep people from 'clicking' on my rollover button

[LindaJimerson]

when a client clicks on my rollover button (only intended to show a second
image) she gets a PAGE NOT FOUND. This is terrible. HELP. If a person
clicks...I don't want ANYTHING TO Happen. THANKS. Linda

[CarlGrint]

Without seeing your code is is purely guess work, but I would assume you have
some form of link for this roll over button which is why the person is able to
click it and return an error.

Check your link field for this button, and maybe place a # in the link field
so that it does not return a real link.


Originally posted by: LindaJimerson
when a client clicks on my rollover button (only intended to show a second
image) she gets a PAGE NOT FOUND. This is terrible. HELP. If a person
clicks...I don't want ANYTHING TO Happen. THANKS. Linda

[jv]

This is a design issue. Your clients are clicking on your rollover
because they have learned to do that from every other website. It's a
lot easier to change your design to conform to what users expect than it
is to go and personally change every user's mind about what should
happen when they see a rollover.

Maybe a rollover isn't the best option if you don't want them to click
on it in the first place. Without seeing your page, of course, it's
hard to know what you want them to do.

jv

CarlGrint wrote:

> Without seeing your code is is purely guess work, but I would assume you have
> some form of link for this roll over button which is why the person is able to
> click it and return an error.
>
> Check your link field for this button, and maybe place a # in the link field
> so that it does not return a real link.
>
>
> Originally posted by: LindaJimerson
> when a client clicks on my rollover button (only intended to show a second
> image) she gets a PAGE NOT FOUND. This is terrible. HELP. If a person
> clicks...I don't want ANYTHING TO Happen. THANKS. Linda
>
>
>

[chuckomalley]

Select the image. In its properties, the Link field should read - javascript:; - and not a URL. # would work as well.

Cheers

Chuck

[Murray *TMM*]

Actually, the octothorpe ("#") can cause problems when used as the target of
a link. If the link is calling a new window, for example, and is close to
the bottom of the calling page, then that page will jump to a non-existant
top of page named anchor when the octothorpe is used.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================

"chuckomalley" <webforumsuser@macromedia.com> wrote in message
news:cuvvl7$j1e$1@forums.macromedia.com...

> Select the image. In its properties, the Link field should read -
> javascript:; - and not a URL. # would work as well.
>
> Cheers
>
> Chuck

[Manuel Socarras]

Linda, i think Murray is right. try:

<A href="JavaScript:void(0)">


Murray *TMM* wrote:

> Actually, the octothorpe ("#") can cause problems when used as the target of
> a link. If the link is calling a new window, for example, and is close to
> the bottom of the calling page, then that page will jump to a non-existant
> top of page named anchor when the octothorpe is used.
>