Change Details

[This is a placeholder card] After the success of https://blog.wikimedia.org/2016/09/19/mobile-web-improvements/ we should explore making the same changes in core (feature flagged of course) as the savings to be had are equally big (if not larger - there is an opportunity to save the cost of running Wikipedia if the bytes savings are significant). Most of the code can easily be upstreamed with the exception of the MobileFormatter logic which would now be able to run in the parser. (NOTE) Blocked on upstream Chromium: <https://bugs.chromium.org/p/chromium/issues/detail?id=875403>

[This is a placeholder card] After the success of https://blog.wikimedia.org/2016/09/19/mobile-web-improvements/ we should explore making the same changes in core (feature flagged of course) as the savings to be had are equally big (if not larger - there is an opportunity to save the cost of running Wikipedia if the bytes savings are significant). Most of the code can easily be upstreamed with the exception of the MobileFormatter logic which would now be able to run in the parser. Blocked on upstreams: * Chromium: <https://bugs.chromium.org/p/chromium/issues/detail?id=875403> * WebKit: <https://bugs.webkit.org/show_bug.cgi?id=224547>

[This is a placeholder card] After the success of https://blog.wikimedia.org/2016/09/19/mobile-web-improvements/ we should explore making the same changes in core (feature flagged of course) as the savings to be had are equally big (if not larger - there is an opportunity to save the cost of running Wikipedia if the bytes savings are significant). Most of the code can easily be upstreamed with the exception of the MobileFormatter logic which would now be able to run in the parser. Blocked on upstreams: (NOTE) Blocked on upstream* Chromium: <https://bugs.chromium.org/p/chromium/issues/detail?id=875403> * WebKit: <https://bugs.webkit.org/show_bug.cgi?id=224547>