On 11/15/18 4:17 PM, Andrea Marchesini wrote:
I think we should implement this API for these reasons:
OK. I guess we should keep an eye on the privacy implications, but
otherwise probably fine to go ahead.
-Boris
___
dev-platform mailing list
dev-
Am Mittwoch, 14. November 2018 22:05:18 UTC+1 schrieb Ryan Hunt:
> Summary:
>
> Scroll anchoring aims to prevent user experience disruptions from content
> loading outside the viewport and causing the page to jump around.
So this will fix stone-old bugs like
https://bugzilla.mozilla.org/show_bug
I think there is value in supporting this API, both for web developers and
for us (e.g. in order to help us deprecate and remove APIs more easily). I
go back and forth on the question of the privacy impact of the API, since
the fact that the reports are exposed both to JS and HTTP layers means tha
On 16/11/2018 12:39, Xidorn Quan wrote:
On Fri, Nov 16, 2018, at 11:12 AM, L. David Baron wrote:
The W3C is proposing a revised charter for:
Web Fonts Working Group
https://www.w3.org/Fonts/WG/webfonts-2018-ac.html
https://lists.w3.org/Archives/Public/public-new-work/2018Oct/0015.html
On Fri, Nov 16, 2018, at 11:12 AM, L. David Baron wrote:
> The W3C is proposing a revised charter for:
>
> Web Fonts Working Group
> https://www.w3.org/Fonts/WG/webfonts-2018-ac.html
> https://lists.w3.org/Archives/Public/public-new-work/2018Oct/0015.html
>
> This is proposing a new work it
5 matches
Mail list logo