Closed Bug 957430 Opened 6 years ago Closed 6 years ago
Stop pretending that Attr
.specified is deprecated
Blink is considering removing this attribute, it would be nice if we did too: <https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ai6_ySyVITg> Bug 661327 added deprecation warnings for this attribute in Firefox 7. Note that the blink-dev thread mentions some usage of this attribute in the wild.
Blink's implementation now matches Firefox in that we print a deprecation warning. I'd like to remove this. Our use counters indicated it's used on 0.04% of pages. Given that the implementation isn't particularly burdensome I expect this is something that won't get removed until usage organically drops.
(In reply to comment #1) > Blink's implementation now matches Firefox in that we print a deprecation > warning. I'd like to remove this. Our use counters indicated it's used on 0.04% > of pages. Given that the implementation isn't particularly burdensome I expect > this is something that won't get removed until usage organically drops. I would really appreciate if you can let us know when you decide to go ahead from removing this from Blink, so that we can remove it from Gecko at the same time as well. Thanks!
So do we want to remove this? Comment #1 indicates there's usage in the wild and that Blink doesn't plan to remove it, IIUC.
Ah good point. I remember there was some chatter about jQuery depending on that actually. Anne, do you know what the current status is?
Flags: needinfo?(ehsan) → needinfo?(annevk)
We cannot remove it. It seems we could clean http://mxr.mozilla.org/mozilla-central/source/dom/webidl/Attr.webidl up a bit to no longer indicate it as extension. And we can remove the warning from http://mxr.mozilla.org/mozilla-central/source/content/base/src/Attr.cpp and maybe do further clean up there too?
We could also leave the warning, the attribute does always return true and is useless therefore. It's not clear to me whether such information would be perceived as useful or a nuisance.
I think it's best to remove the deprecation warning if we're not planning to remove the feature, to prevent warning fatigue etc.
Summary: Consider removing Attr.specified → Stop pretending that Attr.specified is deprecated
Assignee: nobody → ayg
OS: Mac OS X → All
Hardware: x86 → All
Comment on attachment 8411063 [details] [diff] [review] patch Review of attachment 8411063 [details] [diff] [review]: ----------------------------------------------------------------- Please also remove SpecifiedWarning from dom/locales/en-US/chrome/dom/dom.properties and webapprt/locales/en-US/webapprt/overrides/dom.properties. r=me with that.
Attachment #8411063 - Flags: review?(ehsan) → review+
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
Removed the deprecated flag from https://developer.mozilla.org/en-US/docs/Web/API/Attr
You need to log in before you can comment on or make changes to this bug.