[webkit-dev] Removing obsolete File attributes

Eric Seidel eric at webkit.org
Fri Feb 24 13:38:33 PST 2012

My 2¢:

- I'm glad to see these properties go.
- I think Darin is correct to be concerned about a potential
web-compat risk.  (But, I suspect grepping extensions for ".fileSize"
and ".fileName" might actually turn up useful data.  Assuming that's
easy to do?)
- I agree with ap that warnings are mostly useless.  Firefox has a
zillion such warnings, and most page authors seem to ignore them.
- I agree with Jian Li, that if/when we add warnings (or any other
form of deprecation) notating such in the IDL and autogenerating is a
Good Idea™.

How much work is it to collect "how many unique pages grab these"
numbers from nightlies?  Have we done such in the past? (Do we have
other studies to compare against?)  It feels a bit odd for WebKit to
depend on Chromium to collect such numbers, but Chromium does seem
well suited to the task.


On Fri, Feb 24, 2012 at 1:30 PM, Alexey Proskuryakov <ap at webkit.org> wrote:
> 24.02.2012, в 12:20, Darin Fisher написал(а):
> Perhaps a concrete good first step is to log a console warning when they are
> used?  "Warning, blahBlah is a deprecated attribute.  Use fluxCapacitor
> instead."
> I'm not much in favor of such warnings - from all I heard (second or third
> hand, without hard data), they are not effective. FWIW, this is what I'd
> expect - developers don't check console logs for sites they've delivered and
> were paid for long ago.
> I should point out that replacement standard attributes have been
> implemented in WebKit for a long time.
> - WBR, Alexey Proskuryakov
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

More information about the webkit-dev mailing list