Mystical JS weirdness. I tried to override a DOM method in my XBL, e.g., focus(), and it didn't work. The DOM method was called. I now have a pressing need for this to work, namely because it would provide me with an elegant means of fixing text field and autocomplete focus problems. Help!

Nominating for nsbeta3.

Do what now? Draw me a picture of the prototype chain, showing where the property you propose to shadow lives ('focus', e.g.), and the object in which you propose to shadow it (by defining a 'focus' in an object nearer the front of the prototype chain). I can't possibly deal with this bug without hyatt sitting there showing me in a debugger what's going on. So I'm heading in to work to share my retreating germs! In the mean time, I'd rather this bug sit on hyatt's list. Dave, I'll take it the instant we debug it into submission and it turns out to be JS. /be

I don't think it's JS per se... I just need my hand held. I'm feeling clingy.

According to hyatt, this problem is also preventing command controller on a textfield from working correctly in the editor (bug 41810).

nsbeta3+, need to fix to the extent required for bug 41810, which is an nsbeta3+, data-loss scenario.

Seems to have been a bogus bug. It does work. Reverting common dialog to use real focus() and blur() overrides (and not my faked calls).

is this bug really supposed to be resolved? View history shows that hyatt marked it resolved at the same time he marked it nsbeta3+ and set the milestone. That doesn't make sense. Also, the resolution isn't set. If this bug is really supposed to be resolved then it have a resolution. This sounds like another mozilla horking forms problem.

If this bug really isn't supposed to be relsolved, please comment in bug 49306.

It's a bugzilla problem, not a mozilla problem. I used 4.x to resolve this bug as fixed. This keeps happening to me.

Reopening; please mark FIXED or ASSIGNED depending on whether this bug is fixed yet or not. I'm guessing it is not.

> Additional Comments From David Hyatt 2000-08-16 15:50 > > Seems to have been a bogus bug. It does work. Reverting common dialog to > use real focus() and blur() overrides (and not my faked calls). So, I assume INVALID (not a bug). I did put a .focus() method on the XBL binding for <textfield>, and with that in place, my focus() would be called over-riding the DOM focus() method.

verified not-a-bug.