I've seen various number of posts related to the same issue and some
folks think that it's a Mozilla bug (https://bugzilla.mozilla.org/
show_bug.cgi?id=208427) but I'm questioning whether it's really a
jQuery bug that should be addressed by re-evaluating 'withinElement'
where the problem currently seems to manifest rather than waiting for
the Mozilla folks to fix it. FF is after all a very popular browser
and this seems to be an easy bug that will very surface quickly.

Another search I did yielded some results about people discussing this
error due to cross-site scripting exploits and you can not use your
web site to access the objects on a different web site. In my case,
I'm fairly certain (99%) that my own code isn't loading any script
files from other sites so this may not be the problem.

I used to have a page that used YUI tabs and within the tab, a table
for data display and a form. No matter how many times I hovered and
mouse in/out in the input fields, I never saw this error. I then
switched over to jQuery tabs along with Flexigrid in lieu of the tab
and right away, I'm seeing this error on the same form that did not
have this problem earlier.

The problem seems to be that element that receives the event
(event.relatedTarget) is of class type, 'anonymous-div' and somehow,
it's not a node owned by the document from the current site, although
I do not know how.

I've also changed my form from div to table (some folks in one of the
other posts mentioned this) and it had no effect on this bug.

Justin

Reply via email to