Created attachment 573471 [details]
contextMenu bug demonstration
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243
Steps to reproduce:
Here is short HTML for demonstration:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
var contextMenu = 'hello!';
<input type="button" value="click me" onclick="alert(contextMenu)" />
User should click 'click me' button and see alert messages with text 'hello'.
Firefox 8 displays alert message with text 'null'.
Can this variable name clash with the contextMenu feature developed in bug 617528? That one is marked as landed in Firefox 8.
not sure if this is a bug
Yeah, that's unfortunately simply how things work :( I.e. this is what specifications require.
Yeah, this is yet another case when adding new properties to elements break existing pages.
(In reply to Olli Pettay [:smaug] from comment #4)
> Yeah, this is yet another case when adding new properties to elements break
> existing pages.
and a good reason for reworking of the command API spec as we already discussed
Olli, Jonas, do we have a tracker for issues like this?
Reporter, did you run into this on existing site? If so, which one?
(In reply to Boris Zbarsky (:bz) from comment #6)
> Olli, Jonas, do we have a tracker for issues like this?
> Reporter, did you run into this on existing site? If so, which one?
Our clients found this issue on existing business-application which we've developed.
OK. Marking invalid, since the spec requires this behavior... if you feel that the spec needs changing, please raise the issue with the HTML working group?