[Bug 7626] New: Spec says: "Note: Removing an event handler content attribute does not reset the corresponding event handler attribute.". In fact browsers will remove or "deactivate" the listener when you remove the HTML attribute. Some browsers reset it to null or undef

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7626

           Summary: Spec says: "Note: Removing an event handler content
                    attribute does not reset the corresponding event handler
                    attribute.". In fact browsers will remove or
                    "deactivate" the listener when you remove the HTML
                    attribute. Some browsers reset it to null or undef
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-
                    work/#events
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Section: http://www.whatwg.org/specs/web-apps/current-work/#events

Comment:
Spec says: "Note: Removing an event handler content attribute does not reset
the corresponding event handler attribute.". In fact browsers will remove or
"deactivate" the listener when you remove the HTML attribute. Some browsers
reset it to null or undefined, some don't but Gecko/IE/WebKit agree on not
firing events after removeAttribute() was called. (It's considered a bug in
Opera that we differ). -- Hallvord

Posted from: 213.236.208.22


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 15 September 2009 10:27:05 UTC