Skip to content

[css-fonts-3] Request transition to Proposed Recommendation #2795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
svgeesus opened this issue Jun 18, 2018 · 5 comments
Closed

[css-fonts-3] Request transition to Proposed Recommendation #2795

svgeesus opened this issue Jun 18, 2018 · 5 comments

Comments

@svgeesus
Copy link
Contributor

The Fonts 3 testsuite now shows only one failing test which is for font-feature-values. We resolved to remove that feature, deferring it to Fonts 4, which I just did. It was marked as at-risk in the March 2018 CR. I have a one-line pull request on web platform tests which updates the rel=help to point to Fonts 4 instead of Fonts 3.

Once that change is accepted there will be zero failing tests and we have met our CR exit criteria.

I would like a CSS WG resolution to request transition to Proposed Recommendation for Fonts 3.

@svgeesus
Copy link
Contributor Author

Remaining Fonts 3 issues for Disposition of Comments deferred to Fonts 4.

@svgeesus
Copy link
Contributor Author

Disposition of Comments

One remaining open issue, was already at-risk in CR, some uncomfortable with downgrading from must to should. No implementations.

@astearns astearns removed the Agenda+ label Jul 2, 2018
@astearns
Copy link
Member

astearns commented Jul 2, 2018

(removing the Agenda+ label. We'll revisit this once the updated CR gets to the point where we can ask for PR again)

@svgeesus
Copy link
Contributor Author

svgeesus commented Jul 2, 2018

PR transition request
denied due to two small normative changes
Updated CR transition request
spec published 26 June 2018

Exclusion period ends 25 August 2018.

Expect that spec to then move to PR without any edits beyond styling/status

@xfq
Copy link
Member

xfq commented Aug 14, 2018

PR published. Should we close the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants