On May 1, 8:26 pm, Dan <d...@tobias.name> wrote:
>
>
> End the JavaScript with "return false;" and that will suppress the
> jump to the normal href destination.

Good grief! I'd totally forgotten that!!

Yes, it says just so in Chapter 4, Rollover Buttons, of "The Book of
JavaScript, Second Edition!" Damn, in one ear, out the other....

> It's then a good idea to make the href value a URL to a separate page
> with the same content as the attempted popup, so as to make that
> content accessible to non-JavaScript users.

Actually, the href doesn't point to a document, but to text that's
invisible until invoked by an onClick, creating that modal window.

God, what a dilemma! Just what in heck am I supposed to do about
those people (like me!) whose IE7 disabled ActiveX Controls??

> --
> Dan

On May 1, 8:26 pm, Herbert Blenner <a1ea...@verizon.net> wrote:
>
>
> Try using <a href="#" onclick=" . . . ;return false">
>
> Herbert

Many thanks -- for the reminder! Can't believe I forgot that one....

On 01 May 2008, Prisoner at War <prisoner_at_war@yahoo.com> wrote:

> I have a hyperlink that doesn't point to another document, but is used
> to call forth a modal window onClick (or is there another way, without
> text or image links, of calling forth JavaScript on user activity??).

Sure. onmouseover, onmouseout, onsubmit, etc., etc.

> I would like to spare my visitors the inconvenience and visually
> jarring effect of getting thrown back up to the top of the page! =(

--
Neredbojias
http://www.neredbojias.net/
Great sights and sounds

Say, just as an update: it turns out that I was able to achieve
vertical alignment by simply using the position:fixed property and
value, in conjunction with margin:23% (it was originally margin:
400px)....

I may have lucked out, though, as I'm not sure exactly how it's
working in the code I've got (below)...also rather bummed that Sam
Collison's good if dry CSS book didn't discuss the vertical-align
property at all despite listing it in the appendix!


#overlay div
{
width:300px;
margin: 23% auto;
background-color: #fff;
border:1px dashed #000;
padding:15px;
text-align:center;
position:fixed;
left: 38%;
}

Ackk!!

That position:fixed property and value has an odd visual artifact in
Firefox 2! (It has a different one in Opera 9!)

The modal window that's "on" the page is invisible until turned on by
a function that's called onClick -- except when scrolling the webpage,
without having clicked on the hyperlink that calls the function: text
scrolling past that invisible modal window "drags by" in the form of
that modal window! It's like when in the Schwarzenegger movie
"Predator" the alien goes invisible, but you can still see the vague
"shimmer" of its outline, especially when it moves....

In Opera 9, position:fixed causes the bottom half of the text in the
modal window to not display if that modal window pops up below "the
fold" (the halfway scroll-point of a webpage)!

Can somebody tell me what's the matter with all this?? Some kind of
inheritance bugaboo??

#overlay div
{
width:300px;
margin: 23% auto;
background-color: #fff;
border:1px dashed #000;
padding:15px;
text-align:center;
position:fixed;
left: 38%;
}

Scripsit Prisoner at War:

> Hi, People,

People just left after noticing your pointless crossposting without even
setting followups and your continued violation of netiquette when you
comment without quoting what you are responding to. Stay tuned to
getting ignored in future unless you learn some habits.

> Is it possible to have an "empty" or "dummy" <a href> ***without***
> the browser jumping back up the page??

Yes, <a href="#foo" name="foo">. But why would you do that? It's 100.1%
certain that you don't understand what your real problem is and that you
are consequently creating new problems.

> I have a hyperlink that doesn't point to another document, but is used
> to call forth a modal window onClick

So what made you use a link when you don't want to link?

> (or is there another way, without
> text or image links, of calling forth JavaScript on user activity??).

Yes of course. Read any introduction to basics of the elements of using
client-side scripting on www pages. Make sure it's a modern one that
discusses the problem "how do I create the <input type="button"> element
dynamically so that it does not appear when it does not work, i.e. when
scripting is disabled?".

> I would like to spare my visitors the inconvenience and visually
> jarring effect of getting thrown back up to the top of the page! =(

Spare them the nasty effects of creating new windows for them.

Followups set to alt.html.

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

On May 2, 1:52 am, "Jukka K. Korpela" <jkorp...@cs.tut.fi> wrote:
>
>
> People just left after noticing your pointless crossposting without even
> setting followups and your continued violation of netiquette when you
> comment without quoting what you are responding to. Stay tuned to
> getting ignored in future unless you learn some habits.

I don't understand what you mean. How's the cross-posting pointless?
I'm working on my site, which involves CSS and JavaScript in addition
to HTML and general design issues.

> Yes, <a href="#foo" name="foo">.

Hmmm, using a name or id attribute stops the browser from trying to
follow the href the way a "javascript:;" or "return false;" does?
Interesting!

> But why would you do that?

"
I have a hyperlink that doesn't point to another document, but is used
to call forth a modal window onClick (or is there another way, without
text or image links, of calling forth JavaScript on user activity??).
I would like to spare my visitors the inconvenience and visually
jarring effect of getting thrown back up to the top of the page! =(

"
> It's 100.1%
> certain that you don't understand what your real problem is and that you
> are consequently creating new problems.

Very possible. That's why I'm asking around!

> So what made you use a link when you don't want to link?

Well, the user has to have a way of calling forth information in that
modal window. (And no I really do want that information in a modal
window instead of "cluttering" up the rest of my paragraph.)

> Yes of course. Read any introduction to basics of the elements of using
> client-side scripting on www pages. Make sure it's a modern one that
> discusses the problem "how do I create the <input type="button"> element
> dynamically so that it does not appear when it does not work, i.e. when
> scripting is disabled?".

Hmm, an input button! I would need it very small, though...I'm using
a modal window like a footnote, see, or an endnote...I wonder if I can
style that button to be visually minuscule....

> Spare them the nasty effects of creating new windows for them.

But that's the thing -- I don't want a webpage full of footnotes, or
redirect the user to another page full of endnotes. A modal window is
the only way I can think of where somewhat extraneous information can
still be offered...unless...I use some kind of "thought balloon"??
Hey, can I do them Ajax-style onMouseOver balloons with *JavaScript*??

> Followups set to alt.html.

Why? The topic of modal windows and how to best implement them seems
relevant to all the newsgroups I'd chosen.

> --
> Jukka K. Korpela ("Yucca")http://www.cs.tut.fi/~jkorpela/

I hate yucca...it's cactus -- ful for thirst in the desert I
suppose but not a good-tasting plant to cook with!

Followup-To: comp.infosystems.www.authoring.html

On 02.5.2008 г. 04:21, /Thomas 'PointedEars' Lahn/:
> Stanimir Stamenkov wrote:
>> Thu, 1 May 2008 16:16:49 -0700 (PDT), /Prisoner at War/:
>>
>>> I have a hyperlink that doesn't point to another document, but is used
>>> to call forth a modal window onClick (or is there another way, without
>>> text or image links, of calling forth JavaScript on user activity??).
>>> I would like to spare my visitors the inconvenience and visually
>>> jarring effect of getting thrown back up to the top of the page! =(
>>
>> If the element is not really a hyper link why marking it as such?
>> Better use generic SPAN element or A(nchor) element without 'href'
>> and attach 'click' handler to it. This will spare your visitors the
>> confusion with encountering hyper links which are not really hyper
>> links.
>
> However, this reasoning is flawed because the confusion of the user about
> what looks like a control that does not appear to work remains.

I agree HTML Form controls (non-submit buttons) should be used
whenever possible, but as far as I know people avoid them because
they are "harder" to style (they are replaced elements the styling
of which is non-standardized, currently). Styling is the main
reason people abuse hyper links instead of using standard form buttons.

Scripting is used to implement non-standard UI controls, too. The
Google Maps map, for instance. It can't be "expressed" using
standard form controls and it can't possibly work without full
scripting and styling support. In this regard I think it is better
to style a SPAN like a button (or whatever is appropriate) and
attach a custom script action to it, rather than abusing a hyper
link element for that purpose.

--
Stanimir