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

[CSSWG] FPNote request for css-2018 #54

Open
svgeesus opened this Issue Jun 4, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@svgeesus
Contributor

svgeesus commented Jun 4, 2018

Document title, URLs, estimated publication date

CSS Snapshot 2018
https://drafts.csswg.org/css-2018/
next tues or thurs after transition decision

Abstract

This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2018. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.
CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc.

Status

https://drafts.csswg.org/css-2018/#status (as ED)

Link to group's decision to request transition

w3c/csswg-drafts#2388 (comment)

Information about implementations known to the Working Group

All of this is implemented

@plehegar

This comment has been minimized.

Show comment
Hide comment
@plehegar

plehegar Jun 5, 2018

Member

Transition approved.

Member

plehegar commented Jun 5, 2018

Transition approved.

@svgeesus

This comment has been minimized.

Show comment
Hide comment
@svgeesus

svgeesus Jun 6, 2018

Contributor

Some broken links, working with editor to fix

Contributor

svgeesus commented Jun 6, 2018

Some broken links, working with editor to fix

@svgeesus

This comment has been minimized.

Show comment
Hide comment
@svgeesus
Contributor

svgeesus commented Jul 15, 2018

@svgeesus

This comment has been minimized.

Show comment
Hide comment
@svgeesus

svgeesus Sep 16, 2018

Contributor

@frivoal which of the three open issues on Snapshot 2018 need to be fixed before publication? One of them is marked as "needs edits". Should the other two be discussed on a call?
Perhaps closing the Snapshot 2018 meta issue I opened was a bit premature, in retrospect.

Contributor

svgeesus commented Sep 16, 2018

@frivoal which of the three open issues on Snapshot 2018 need to be fixed before publication? One of them is marked as "needs edits". Should the other two be discussed on a call?
Perhaps closing the Snapshot 2018 meta issue I opened was a bit premature, in retrospect.

@frivoal

This comment has been minimized.

Show comment
Hide comment
@frivoal

frivoal Sep 26, 2018

We're down to two, and I've put both of them on agenda+.

frivoal commented Sep 26, 2018

We're down to two, and I've put both of them on agenda+.

@svgeesus

This comment has been minimized.

Show comment
Hide comment
@svgeesus

svgeesus Sep 26, 2018

Contributor

Thanks, @frivoal

Contributor

svgeesus commented Sep 26, 2018

Thanks, @frivoal

@frivoal

This comment has been minimized.

Show comment
Hide comment
@frivoal

frivoal Oct 10, 2018

We're down to 0 open issues. Publish away.

Note: We have not (yet) reached agreement on doing away with the current dated shortname scheme, so (for this year at least) do publish under TR/css-2018/

frivoal commented Oct 10, 2018

We're down to 0 open issues. Publish away.

Note: We have not (yet) reached agreement on doing away with the current dated shortname scheme, so (for this year at least) do publish under TR/css-2018/

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