This only happen in Netscape.
IE will display the text in the alt setting (alt="text")


"Hill, Les" <[EMAIL PROTECTED]> wrote:
>> Eli,
>> 
>> This is a particularly ugly aspect of the way ND interacts with browsers.
>> I'll try and explain the interaction and give you some pointers on how to
>> get around the "ugly aspect".
>> 
>> Almost all ND interactions are through HTML/HTTP forms (I am ignoring
>> HREFs here :).  A form uses the HTTP POST method to send information from
>> the browser to the server.  The browser packages up all the HTML form
>> information into consecutive name value pairs (Name=Value) which are
>> passed as data to the ACTION tag specified on the form.  When a button is
>> pressed on a form, the pressed buttons name value pair is passed along,
>> all other buttons are ignored.
>> 
>> The ND generated ACTION tag looks something like this
>> ACTION="../myProject/myPage" -- this by default invokes the pages default
>> display behavior (try putting a submit button in a page's  HTML template
>> to see that work).  In order to differentiate between the various buttons
>> on a page (and consequently the methods available on the page), ND sets
>> the name to the name of the method and a parameter -- something like
>> NAME="onMyButtonWebEvent(MyButton)".
>> 
>> When a name value pair matching that pattern* is seen in by ND, the
>> matching method on the page is invoked passing the argument along (after
>> processing all the incoming name value pairs of course).
>> 
>> This has been the way ND works for a very long time (perhaps even since
>> v1).  When the v4 browsers arrived with tool tips, there was no standard
>> on how to control the contents of the tool tips on buttons, so the
>> browsers used the name of the button.  This leads us to the "ugly aspect",
>> ND's reliance on the name of the button conflicts with the browsers v4
>> (v3+?) behavior.
>> 
>> From the above, it is obvious that what needs to be done to clear up the
>> mess is change the name of the buttons.  However, if you do that, then ND
>> stops working!
>> 
>> Enter Javascript.
>> 
>> Using Javascript, you can set up an onClick handler for every button,
>> allowing you to change the names at the moment of the click to something
>> ND will understand.
>> 
>> The particular implementation that I developed works like this:
>> 
>> - every page has an additional static text field at the top of the page
>> that spits out a Javascript handleClick() function and a HIDDEN whose name
>> is REPLACEME
>> 
>> - every button has been changed to return HTML+ that looks like <A
>> HREF="/hasnoJavascript.html"
>> onClick="handleClick('onOriginalNameWebEvent(OriginalName)'); return
>> false;"><INPUT NAME="Pretty name" VALUE="OriginalName"></A>
>> 
>> - handleClick() then changes the name of the HIDDEN named REPLACEME to the
>> argument passed in and submits the form.
>> 
>> ND WISHLIST: Of course this could be handled from within ND by changing
>> the way it currently works.  Adding a mapping from "Pretty Name" to method
>> on every page would solve this problem "under the hood".
>> 
>> Good luck.
>> 
>> *exact mechanism is unclear -- hashtable? reflection on every event? who
>> knows?
>> +I found that using the <A> around the button was necessary to get my
>> particular handler to work, you should try it without :)
>> 
>> [EMAIL PROTECTED]
>> Team NetDynamics
>> 
>> -----Original Message-----
>> From:        [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
>> Sent:        Wednesday, April 28, 1999 7:57 AM
>> To:  [EMAIL PROTECTED]
>> Subject:     [ND] Popup window on ND buttons
>> 
>> Why, when browsing my ND app using Netscape (but not IE) do I get a popup
>> window (tooltip) whenever I move the mouse
>> over buttons I've created using ND?  The popup string consists of the name
>> of the handler function that ND will call when the
>> user clicks on the button.
>> 
>> How can I get rid of this?
>> 
>> Eli
>> [EMAIL PROTECTED]
>> 
>> _________________________________________________________________________
>> 
>> For help in using, subscribing, and unsubscribing to the discussion
>> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>> 
>> For dire need help, email: [EMAIL PROTECTED]

_________________________________________________________________________

For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html

For dire need help, email: [EMAIL PROTECTED]

Reply via email to