On Tue, Mar 8, 2016 at 8:22 AM, Andrew Overholt <overh...@mozilla.com> wrote: > Implement Client-Hints HTTP header > https://bugzilla.mozilla.org/show_bug.cgi?id=935216
Client-Hints is negotation on the HTTP layer that goes beyond reversible bit transformation (i.e. it's not like gzip or Brotli). I continue to believe that negotation mechanisms that the layout part of the engine is aware of are superior to pushing the negotiation to the networking layer. See https://wiki.whatwg.org/wiki/Why_not_conneg for an example how the <source> children of <video> and <audio> are superior to HTTP-layer negotation (although https is making non-CDN proxies irrelevant). So I continue to think that Client-Hints is architecturally bad. For images, <picture> and srcset exist and are superior. For CSS, I continue to think we should add a mechanism for <link rel=stylesheet> to opt out of synchronous CSSOM and sheets that opt out of synchronous CSSOM and whose media query doesn't match should not be fetched. I continue to be opposed to Client-Hints as far as the merits of the feature go. However, I prioritize Web compat over good architecture, so if sites deploy Client-Hints to Chrome such that it becomes a Web compat problem for us, I think we should probably implement the feature to neutralize the Web compat threat. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
