Skip to content

[css-inline-3] Is alignment-baseline missing the hanging value? #13327

Closed

Description

@kbhomes

The dominant-baseline property has the following values:

auto | text-bottom | alphabetic | ideographic | middle | central | mathematical | hanging | text-top 

And the alignment-baseline property has the following values:

baseline | text-bottom | alphabetic | ideographic | middle | central | mathematical | text-top 

Besides auto and baseline, they're identical except alignment-baseline is missing hanging. I assume that it's meant to have it, especially since it was an accepted value in SVG 1.1 and it is not listed as having been removed in SVG 2.

I can submit a small PR to put the hanging value into alignment-baseline if this is the case.

Activity

  1. SebastianZ commented on Jan 18, 2026

    @SebastianZ
    Contributor

    It seems this discrepancy is already there since those properties got introduced in 107993a.
    @fantasai Is this intentional or just an oversight?

    Sebastian

  2. SebastianZ commented on Jan 19, 2026

    @SebastianZ
    Contributor

    If it's an oversight, we should probably move all the keywords (except auto and baseline) to a new data type and reference it in both properties to avoid future discrepancies between them.

    Sebastian

  3. kbhomes commented on Feb 2, 2026

    @kbhomes
    ContributorAuthor

    In case they are meant to be the same, I made a proposed edit to the css-inline-3 spec in my fork that follows @SebastianZ's suggestion in the previous comment. I pulled out the baseline metrics into a new type and used them in both dominant-baseline and alignment-baseline; this is modeled after the existing <text-edge> type and associated language of the line-fit-edge and text-box-edge properties.

    I haven't submitted this for a PR yet since this issue isn't resolved, but I can publish one if that's what we align on. 🙂

  4. SebastianZ commented on Feb 5, 2026

    @SebastianZ
    Contributor

    @kbhomes I'd say just create the PR and I request an async resolution to accept it (unless @fantasai jumps in and merges it early.😄)

    So, proposed resolution: Accept @kbhomes' PR, merging the keywords from dominant-baseline and alignment-baseline (except auto and baseline) and thus adding hanging to alignment-baseline.

    Sebastian

  5. SebastianZ commented on Feb 5, 2026

    @SebastianZ
    Contributor

    Ah, and @kbhomes, please also add a note to the Changes section when creating the PR!

    Sebastian

  6. kbhomes commented on Feb 5, 2026

    @kbhomes
    ContributorAuthor

    Thanks @SebastianZ! I've published the PR including the new bullet in the Changes section. Got blocked by the IPR commitment check, I just created the W3C account and linked to my GitHub but I think a maintainer needs to re-run the validation?

  7. SebastianZ commented on Feb 7, 2026

    @SebastianZ
    Contributor

    I already re-ran the validation, though to merge it you also have to join the CSSWG as a member. Or, depending on whether the missing hanging value is seen as an oversight, the PR could also be marked as non-substantive.

    Sebastian

  8. astearns commented on Feb 9, 2026

    @astearns
    Member

    The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment.

    Proposed Resolution: Add hanging to alignment-baseline to match dominant-baseline

  9. astearns commented on Feb 16, 2026

    @astearns
    Member

    RESOLVED: Add hanging to alignment-baseline to match dominant-baseline

  10. 3 remaining items

  11. kbhomes commented on Feb 16, 2026

    @kbhomes
    ContributorAuthor

    FYI I'll be adding WPTs for this as part of the Firefox implementation of dominant-baseline (bug 2015279) and alignment-baseline (bug 1403440).

    @SebastianZ Would we be able to move ahead with merging the spec edit as non-substantive? I tried to see if I could submit an IPR commitment, but it appears I can only join the CSSWG as either an invited expert (which I'm not) or as part of my employer's organization (which I can't since I'm not representing them in any of this work).

  12. SebastianZ commented on Feb 17, 2026

    @SebastianZ
    Contributor

    @SebastianZ Would we be able to move ahead with merging the spec edit as non-substantive? I tried to see if I could submit an IPR commitment, but it appears I can only join the CSSWG as either an invited expert (which I'm not) or as part of my employer's organization (which I can't since I'm not representing them in any of this work).

    @astearns @svgeesus Is it ok to just merge the related PR #13456?

    Sebastian

  13. astearns commented on Feb 17, 2026

    @astearns
    Member

    There should be a way to provide an individual IPR commitment. I reset the bot - could you try again, @kbhomes?

  14. kbhomes commented on Feb 17, 2026

    @kbhomes
    ContributorAuthor

    @astearns Hmm, I'm not seeing a way to do that. The IPR check details link says:

    kbhomes did not make IPR commitments for this group. To make the IPR commitments, kbhomes should join the Cascading Style Sheets (CSS) Working Group .

    Clicking the join link takes me to the CSSWG page with the message:

    There is a problem
    You cannot join the group. See instructions

    The instructions link gives me details for the two options that don't work for me — Invited Expert or represent an organization.

  15. svgeesus commented on Feb 17, 2026

    @svgeesus
    Collaborator

    There should be a way to provide an individual IPR commitment

    I just requested an individual IPR commitment

  16. kbhomes commented on Feb 17, 2026

    @kbhomes
    ContributorAuthor

    @svgeesus Thanks! Got the request and signed the commitment. Will the IPR check in #13456 automatically update or does it need to be revalidated?

  17. svgeesus commented on Feb 17, 2026

    @svgeesus
    Collaborator

    Commitment received. However the IPR bot, on being asked to revalidate, now says

    JSON.parse: unexpected character at line 1 column 1 of the JSON data

    Sigh, sorry for the inconvenience.

  18. kbhomes commented on May 28, 2026

    @kbhomes
    ContributorAuthor

    My new WPTs for alignment-baseline were merged from Firefox a couple weeks back: web-platform-tests/wpt#59796. This includes testing for the new hanging value. With that and the spec change I did in #13456, I think this issue can be closed out.

  19. SebastianZ commented on May 28, 2026

    @SebastianZ
    Contributor

    Then let's do that.😄

    Thank you for your hard work related to this, @kbhomes!

    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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions