I managed to narrow down the source of the "Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead." warning that I see occasionally - looks like having a DOMAttrModified event listener around causes that warning if the event listener is triggered. See attached testcase that does nothing other than adding this event listener and triggering it. This is enough to cause this warning to pop up in Error Console. Tested with Firefox 8 and current 11.0a1 nightly on Windows 7 x64.
This is kind of ok, since also DOMAttrModified is deprecated. Need to add a warning about using DOMAttrModified once we have the replacement done.
I'm using it because it appears to be the only way to get notified when <xul:tree> finishes editing ("editing" attribute is removed).
DOMAttrModified deprecated? Maybe there needs to be a replacement first?
The Lightning calendaring extension for Thunderbird triggers the same warning because it is using DOMAttrModified too (http://mxr.mozilla.org/comm-central/search?string=DOMAttrModified&find=/calendar/) When is it going to be removed? What should be used instead?
We shouldn't spam the warning until the replacement is available. Even if we want some kinds of warnings, the current message does not indicate what actually cause the warning.
Attachment #600100 - Flags: review?(bugs)
Autoland Patchset: Patches: 600100 Branch: mozilla-central => try Destination: http://hg.mozilla.org/try/pushloghtml?changeset=f2ffdd8bfda3 Try run started, revision f2ffdd8bfda3. To cancel or monitor the job, see: https://tbpl.mozilla.org/?tree=Try&rev=f2ffdd8bfda3
Try run for f2ffdd8bfda3 is complete. Detailed breakdown of the results available here: https://tbpl.mozilla.org/?tree=Try&rev=f2ffdd8bfda3 Results (out of 215 total builds): exception: 4 success: 175 warnings: 21 failure: 15 Builds (or logs if builds failed) available at: http://email@example.com
Assignee: nobody → VYV03354
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
You need to log in before you can comment on or make changes to this bug.