Hi Adam. I just read through the Bugzilla bugs on this topic. Hopefully, I'm a mostly neutral observer.
> We should remove deprecatedFrameEncoding. Removing the code has the > following benefits: > > 1) Standards compliance. To me, this seems like your strongest argument. However… > b) Most user agents, including most browsers, do not have this > behavior. Is this true? In Bugzilla, I saw Alexey request cross-browser testing, but I didn't see any testing results, other than Alexey's testing of Firefox 9, which did have this behavior. So, the tested user agent compatibility score seems to be 2-1 (Safari and Firefox vs Chrome). Browser compatibility seems to be Alexey's strongest argument for not following the HTTP working group's consensus. If there were no tradeoff between the working group's consensus and browser compatibility, I suspect that Alexey's position might change. Can you supply more information here? Which web browsers have been tested, what were the tests, and what were the results? > 2) Stability. This code crashes. This argument seems like a red herring to me. We should make a decision about deprecatedFrameEncoding on its merits. If deprecatedFrameEncoding is the right behavior for WebKit, let's fix the crashes. If deprecatedFrameEncoding is the wrong behavior for WebKit, let's remove it. Either way, crashes aren't the deciding factor. Best, Geoff _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
