Skip to content

[css-text-3][css-fonts-3][css-text-decor-3] Distinguish applying to text vs applying to boxes #5303

Closed

Description

@fantasai

We've historically only used the 'Applies to' lines to apply to boxes, but it seems we do need to distinguish whether something applies to an inline box vs. line box vs. text:

  • For ::marker, a lot of properties don't apply to the marker box, because we don't know what kind of box an outside marker is yet. But they should inherit through to the text and apply there.
  • For display: contents, properties can be applied to an element that generates no box, but still be pass through to its text.

So I'm thinking we should update the propdef tables of properties that apply to text to say "and text", so we can better define how these cases work. I think the rough idea is to do that for:

  • color (and maybe all of css-color-adjust?)
  • all font properties
  • all inheritable css-text-decor properties
  • all properties in css-text that apply to inline boxes?

and, going forward, not do that for any properties that rely on knowing box geometry.

(See https://www.w3.org/TR/css-display-3/#intro for discussion of boxes/elements/text runs etc.)

Does this make sense?

Activity

  1. frivoal commented on Dec 3, 2020

    @frivoal
    Collaborator

    Proposed PR in #5761

  2. added a commit that references this issue on Dec 9, 2020
  3. css-meeting-bot commented on Dec 9, 2020

    @css-meeting-bot
    Member

    The CSS Working Group just discussed [css-text-3][css-fonts-3][css-text-decor-3] Distinguish applying to text vs applying to boxes.

    The full IRC log of that discussion <dael> Topic: [css-text-3][css-fonts-3][css-text-decor-3] Distinguish applying to text vs applying to boxes
    <dael> github: https://github.com//issues/5303
    <dael> fantasai: Looks like chris mirged the PR. This will change applies to line for as many specs as I can think of. I guess heads up it's merged. There were questions about writing modes where so far text-combine-upwrite does apply
    <dael> fantasai: css 3 text we're getting toward 0 issues. If i18n and tag sign off I'll ask to transition next week
    <chris> s/mirged/merged/
    <dael> florian: On testing front we're doing pretty good. Large amount of tests and gaps documented. We have test for many things. Don't need all for CR.
    <dael> astearns: Any other bits on this?
    <fantasai> s/does apply/does apply and writing-mode does not/
    <dael> astearns: It was just informative? No resolutions?
    <fantasai> https://github.com//issues/5303
    <dael> fantasai: I guess if we want to close 5303 which is the bug
    <dael> astearns: Since PR is merged yes I assume
    <dael> florian: Might have missed some, but none was wrong. Can open new issue for anything missed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions