Re: [csswg-drafts] [css-fonts-3] Default feature list should not require a list of features to turn on

I committed some tests for this section (each has several subtests). I believe these test everything that this section mandates. Here are the results:

Firefox and Chrome pass all tests, so we do have interop there. Safari passes most subtests but not all, which does lead to failing each test it t's entirety. Edge does not currently implement this so naturally fails all the tests.

I agree with David that allowing implementations to exceed the requirements (can do better) is noble and also testable and workable. Watering down the spec to `may` is unfortunate for content developers, because they then have to set a bunch of stuff just to get interop between browsers.

GitHub Notification of comment by svgeesus
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 10 January 2018 15:17:10 UTC