From 710c48f908290c52b93e57e29741fcd0696b2d22 Mon Sep 17 00:00:00 2001 From: Thomas Keil Date: Thu, 4 Jan 2007 22:29:18 +0000 Subject: *** empty log message *** --- javascript/examples/example10.html | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 javascript/examples/example10.html (limited to 'javascript/examples/example10.html') diff --git a/javascript/examples/example10.html b/javascript/examples/example10.html new file mode 100644 index 0000000..0d35f3d --- /dev/null +++ b/javascript/examples/example10.html @@ -0,0 +1,34 @@ + + + + [DOM Tooltip] Example 10: Onload PopIn + + + + + + + +
Example 10: Onload PopIn
+
+

Okay, I know that some of you aren't going to like what you see in this example, but you have to admit, it is better than a popup window and can be used in a positive way without being too intrusive. So here is my introduction...

+

If you don't want to annoy users with a popup window, but you do want to alert the attention of your audience, this can be a nice middleground. Simply add the domTT_activate() call to the onload handler (or at any arbitrary time) and specify and 'x' and 'y' position for your tooltip (or else it will end up in the upper left corner). When creating tooltips that are not associated with a javascript event, the second parameter to domTT_activate() should be set to null.

+

Close windows

+

* The second popup uses a custom close link in its content.

+
+
«Example 9
Example 11»
+ + -- cgit v1.2.3