Skip to content

-webkit-image-set() might be a requirement to be compatible.  #144

Closed

Description

@karlcow

Activity

  1. karlcow commented on May 5, 2021

    @karlcow
    MemberAuthor
  2. foolip commented on May 6, 2021

    @foolip
    Member

    Looks like the spec for this is https://drafts.csswg.org/css-images-4/#image-set-notation.

    Should the prefixed variant be defined to behave exactly the same, or are there differences? @schenney-chromium do you know?

  3. schenney-chromium commented on May 6, 2021

    @schenney-chromium

    We would have a long road to remove the prefixed version because it is used in many Chrome and ChromeOS UI pages. Any change short of removing would also be challenging.

    Fortunately, based on my understand of the parsing code and the spec, the -webkit-image-set spec is a syntactically valid subset of the image-set spec and the spec gives us a lot of scope in how to decide which image to use. So I don't see a need to adjust any spec based on back-compat and the implementation of image-set will be somewhat easier.

  4. emilio commented on May 12, 2021

    @emilio

    I think w3c/csswg-drafts#6285 is the most trivial way to go forward with this in terms of complexity of both specifications and implementations.

  5. added a commit that references this issue on May 12, 2021
  6. gsnedders commented on Jun 6, 2022

    @gsnedders
    Member

    This can be closed, as w3c/csswg-drafts#6285 defined this in the CSS Images spec.

  7. miketaylr commented on Jun 6, 2022

    @miketaylr
    Member

    Awesome.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions