PSA: Firefox Nightly now with experimental Wayland support

2018-11-15 Thread Mike Hommey
Hi, As of last nightly (20181115100051), Firefox now supports Wayland, thanks to the work from Martin Stransky and Jan Horak, mostly. Before that, it was possible to build your own Firefox with Wayland support (and Fedora does it), but now the downloads from mozilla.org come with Wayland support

Proposed W3C Charter: Web Fonts Working Group

2018-11-15 Thread L. David Baron
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 item for the group, Progressive Font Enrichment, to allow progressive

Re: Intent to implement: Reporting API

2018-11-15 Thread Andrea Marchesini
There is a proposal to support "report-only" violations for feature policy: https://github.com/WICG/feature-policy/blob/824de86f89599240c24b5ae3cd58d25984446af5/reporting.md I think we should implement this API for these reasons: a. it unifies the reporting of violations and interventions. At

Re: Intent to implement: Reporting API

2018-11-15 Thread Boris Zbarsky
On 11/15/18 9:52 AM, Ehsan Akhgari wrote: The idea is to use Feature Policy in report-only mode There is no report-only mode in the Feature Policy spec, nor in our implementation. See the note at the end of https://wicg.github.io/feature-policy/#reporting So I'm back to my question: is

Re: Intent to implement: Reporting API

2018-11-15 Thread Ehsan Akhgari
On Wed, Nov 14, 2018 at 11:20 AM Boris Zbarsky wrote: > On 11/13/18 4:33 AM, Andrea Marchesini wrote: > > I decided to implement this API, because it is required in the > > web-platform-tests for FeaturePolicy. > > Is it needed for any other reason? If not, this seems like a bug in the > tests: