On Fri, Feb 24, 2012 at 1:47 PM, Jochen Eisinger <joc...@chromium.org>wrote:
> > > On Fri, Feb 24, 2012 at 10:38 PM, Eric Seidel <e...@webkit.org> wrote: > >> 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. >> > > Is it really useless, or does it help to decrease the number of new pages > using the feature? At the very least, it would make it seem more fair if > the feature is eventually removed to give some warning. > Exactly! For a point of reference, the bug to remove these properties caught the attention of a developer at Google just yesterday. He was really worried that we were taking away the ability to get the "name" and "size" from a File. He just wasn't aware of the fact that the same data was still available, but just under a different name on the Blob interface. He was writing new code. I'm certain a warning in the console would have been helpful in this case. > >> - 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™. >> > > I agree that this would be useful. > > Great idea! -Darin > -jochen > > >> >> 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. >> >> -eric >> >> On Fri, Feb 24, 2012 at 1:30 PM, Alexey Proskuryakov <a...@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@lists.webkit.org >> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> > >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
