Re: [ANN] hoverMe 3.0 -- An Even More Sophisticated Image Hover Script

Martin Honnen wrote:

> Thomas 'PointedEars' Lahn wrote:
>> <URL:http://pointedears.de/hoverMe>
>
> Mouse over/out the "About" causes
>
> Error: uncaught exception: [Exception... "Component returned failure
> code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMEventTarget.dispatchEvent]"
> nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
> http://pointedears.de/scripts/test/debug.js :: printfire :: line 249"
> data: no]
>
> with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2)
> Gecko/20040804 Netscape/7.2 (ax)

Thanks, I see it also with my Netscape 7.2 now. That was a minor bug in
debug.js, rather unrelated to hoverMe. printfire(), which writes to the
FireBug error console, was taken as-is from Joe Hewitt's Web site, and
apparently he did not test with Netscapes. (Well, FireBug is a _Firefox_
extension after all.)

But as I said, you don't have to include debug.js for hoverMe (3.0). That
is only needed if you want FireBug debug messages as you hover over the
link/image. Despite the unhandled exception, the rollover effect should
work (it does in my Netscapes).

I have fixed this bug in debug.js 0.99.6.2006041619 now, however the fix
requires that you include types.js, as it provides the *ErrorHandler()
methods required, if you want to make use of printfire() from debug.js.
Hence a slight change of the test case HTML, too, and consequently of the
HTML diff.

(Another solution is that you copy printfire() from debug.js into a `script'
element in your HTML markup or into hoverMe-3.0.js [for the latter, you
must obey the GNU GPL]. I would rather not do that by default, as I
dislike duplicating source code, and the separation was done intentionally:
usually one does not want to debug hoverMe in FireBug, and so does not
include debug.js in the first place.)

Regards,
PointedEars
Received on Mon May 1 05:03:13 2006