Skip to content

[css-values-3][spec-rec] Publish CSS Values & Units 3 as a REC #4846

Open
Open
[css-values-3][spec-rec] Publish CSS Values & Units 3 as a REC#4846
Labels
css-values-3meta

Description

@gsnedders
gsnedders
opened on Mar 7, 2020

From @atanassov's last email, given having something public to point at about what blocks publishing it would be nice:

AIUI the blockers status are:

  • Write as DOC for the 2019 CR
  • [css-values-3] Drop the Values 3 version of attr() back to single-arg form #4840 (drop the at-risk multi-arg attr())
  • Check references v. the normative reference policy; currently non-REC normative refs:
    • [CSS-CASCADE-4]
    • [CSS-COLOR-4]
    • [CSS-COUNTER-STYLES-3]
    • [CSS-DISPLAY-3]
    • [CSS-IMAGES-4]
    • [CSS-OVERFLOW-3]
    • [CSS-SIZING-3]
    • [CSS-UI-4]
    • [CSS-VALUES-4] (note this is a normative citation from level 3 to level 4!)
    • [CSS-WRITING-MODES-4]
    • [CSS3-BACKGROUND]
    • [CSS3-IMAGES]
    • [CSS3CASCADE]
    • [CSS3PAGE]
    • [CSS3SYN]
    • [CSSOM]
    • [MEDIAQ]
    • [SELECTORS-4] (note we also cite [SELECTORS-3] which is a REC)
  • Check test suite status and write an implementation report

Activity

  1. gsnedders
    added
    css-values-3
    meta
    on Mar 7, 2020

  2. svgeesus commented on Mar 9, 2020

    @svgeesus
    svgeesus
    on Mar 9, 2020
    Collaborator

    Check test suite status and write an implementation report

    The report is automatically generated. Here is the current one (39 of 70 required tests meet CR exit criteria).

    The main things missing are passes on ch units in both horizontal and vertical writing.

    There are also missing test results for Blink, Webkit (and also Edge, if anyone has a pre-Blink Edge around for testing)

  3. svgeesus commented on Mar 9, 2020

    @svgeesus
    svgeesus
    on Mar 9, 2020
    Collaborator

    Currently 6 open, 41 closed issues (one of them being this meta-issue).

  4. gsnedders commented on Mar 9, 2020

    @gsnedders
    gsnedders
    on Mar 9, 2020
    MemberAuthor

    The report is automatically generated. Here is the current one (39 of 70 required tests meet CR exit criteria).

    Well, yes, but I've almost never seen an implementation report accepted without any sort of human-written element explaining failures. :)

    Currently 6 open, 41 closed issues (one of them being this meta-issue).

    FWIW, it wasn't clear how many of those are things that actually block Level 3?

  5. gsnedders commented on Mar 9, 2020

    @gsnedders
    gsnedders
    on Mar 9, 2020
    MemberAuthor

    and also Edge, if anyone has a pre-Blink Edge around for testing

    https://wpt.fyi/results/css/css-values?label=master&product=edge-44.17763.1.0&product=chrome%5Bstable%5D&product=firefox%5Bstable%5D&product=safari%5Bstable%5D&aligned has results for 4b7986331d2e2ee1e63ed42e392d36946904327c, which is admittedly now a while ago.

  6. svgeesus commented on Mar 10, 2020

    @svgeesus
    svgeesus
    on Mar 10, 2020
    Collaborator

    Now 57 of 70 required tests meet CR exit criteria Problems are ch unit, especially in vertical writing; calc in transform; calc in offset-position, and calc in text-combine-upright: digits .

    I suspect carefully checking the correctness of those tests, then filing individual bugs on browser engines, would help drive those fails towards zero.

    And yes, a human-written addendum that the fails are more to do with the other specs being tested (this is particularly true with a spec like V&U) will be needed.

  7. svgeesus commented on Mar 10, 2020

    @svgeesus
    svgeesus
    on Mar 10, 2020
    Collaborator

    I removed the css-values-3 tag on #4329 and the rest look like low-hanging fruit that could be closed off speedily.

  8. svgeesus commented on Mar 10, 2020

    @svgeesus
    svgeesus
    on Mar 10, 2020
    Collaborator

    [CSS-VALUES-4] (note this is a normative citation from level 3 to level 4!)

    Okay that is a bit whacked.

     [css-values-4] defines the following terms:
%
angle
frequency
integer
length
number
string
time
toggle()
url

    I'm guessing that is incorrect bikeshed syntax, and should be fixed.

  9. tabatkins commented on Mar 10, 2020

    @tabatkins
    tabatkins
    on Mar 10, 2020
    Member

    It can be fixed manually (using link-defaults), but the reason it's happening is that I currently only distinguish between "ED" and "TR" statuses for definitions; I don't go into more fine-grained divisions within TR. As such, Values 4 is considered a perfectly suitable definition source.

  10. svgeesus commented on Jul 31, 2024

    @svgeesus
    svgeesus
    on Jul 31, 2024
    Collaborator

    So (four years later):

    Assessing the level of implementation support is tricky because the values and units can't be implemented by themselves; the actual WPT are examples where other specifications are using them. There is a manually generated implementation report but that was last updated April 2021.

    @tabatkins @fantasai how close do you think this is to getting to REC? It would need another CR Snapshot first, of course.

  11. svgeesus commented on Oct 17, 2025

    @svgeesus
    svgeesus
    on Oct 17, 2025
    Collaborator

    Seems pretty static, now 3302 tests.

    Image

    and changes not updated but almost no changes since last CRS

    ACR draft was published in 2024 so @fantasai @tabatkins how much plea-bargaining would an implementation report have to do to be able to exit CR? It seems tht Firefox is still in the lead, so we need one other implementation to improve.

    And should we publish a CR Snapshot to incorporate the one tiny but non-editorial change?

  12. gsnedders commented on Oct 17, 2025

    @gsnedders
    gsnedders
    on Oct 17, 2025
    MemberAuthor

    A quick glance at tests with less than two passes suggests that it's mostly things in later levels which don't pass.

    It would be both easier to understand where things stand if there were subdirectories corresponding to the different sections of the spec, rather than having 285 files in a single directory, and easier to exclude additions from Level 4 and Level 5.

  13. SebastianZ commented on Oct 18, 2025

    @SebastianZ
    SebastianZ
    on Oct 18, 2025
    Contributor

    Looking at the main portion of failing tests in the spec, they refer to values in CSS Shapes like https://wpt.fyi/results/css/css-shapes/shape-outside/values/shape-outside-circle-004.html?label=master&label=experimental&aligned.

    And skimming through those tests, the results basically seem ok - Blink and WebKit either try to be smart about the computed value or just return the authored value - though those sometimes differ from the expected value, which often uses (unnecessary) calc() expressions.

    For what it's worth, there's also a Chromium bug related to those tests.

    Sebastian

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    css-values-3meta

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions