Tree Branches for Mozilla 1.3

Saturday February 22nd, 2003

Yesterday, the tree was branched in preparation for the final release of Mozilla 1.3. Checkins to the 1.3 branch are being tightly controlled by Meanwhile, the trunk has been reopened for 1.4 Alpha development. See the Roadmap for more details and tinderbox for the current status of the 1.3 branch and the trunk. A list of bugs blocking the 1.3 release is also available.

#34 Re: Re: Re: Re: Re: Re: A missing DHTML bug

by jvlb

Sunday February 23rd, 2003 7:45 AM

You are replying to this message

Thanks for the explanation and I do see your point. I think the common expectation would be for the event to bubble to the containing element, in this case the "a" element. I appreciate that the act of swapping visibility can confuse the issue regarding the click event and I wish I could offer an easy solution. It would seem that somehow the event needs to be trapped and forced up the DOM tree to the containing node. I note that the examples you have produced differ significantly (at least conceptually) from mine, in that you are placing "div" elements in the same space with separate event handlers. The major departure here is that in my markup the event handlers are all part of a containing block element. That is why I would expect my code to work, though I would expect problems with your implementation. It seems strange that the event handlers, which are part of the containing tag, execute, but the function of the tag itself does not. If the event handlers were on the "img" tags, it would be more like your example and the failure of the event to reach the containing element would make more sense. I certainly appreciate the time you have taken in addressing this issue and hope the solution proves to be less radical than you fear. If there is any assistance I can provide, please don't hesitate to ask. I feel a certain ownership of this bug and am willing to do whatever I can to help resolve it. Unfortunately, my programming knowledge does not extend to C.