2.58 KB, text/html
Created attachment 102146 [details] Shows onchange firing, onattrmodified filing to fire. Also demonstrates two distinct bugs, which I'll file separately
Created attachment 102158 [details] Shows onchange firing, onattrmodified filing to fire. Also demonstrates two distinct bugs, which I'll file separately. Please delete/ignore first attachment. I lost a variable when simplifying the script.
Comment on attachment 102158 [details] Shows onchange firing, onattrmodified filing to fire. See bug 173255 and bug 173270.
> DOMAttrModified [must be f]ired after an Attr has been > modified on a node. The target of this event is the Node whose Attr changed. Changing the presentational value of a form control does *not* change the HTML value attribute. It changes the DOM value attribute on the element, but that is not an Attr.
Still, onchange shouldn't be firing: "The onchange event occurs when a control loses the input focus _and _its value has been modified since gaining focus..." (http://www.w3.org/TR/html401/interact/scripts.html#h-18.2.3)