w3c / w3c/csswg-drafts

[css-images-4] Should `CSS.elementSources` be considered at risk?

Open
#9,372 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-images-4
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

Can you please clarify if you plan to drop CSS.elementSources? or even image()?

CSS.elementSources was hidden before #3572, which defined it with any as its type.

partial namespace CSS {
 [SameObject] readonly attribute any elementSources;
};

In #428, fixed by the above PR:

that spec version is way out of date and needs to get some stuff dropped.

If it should not be dropped, is there a reason to not define it as a maplike?

EXAMPLE 13

<script>
  var bg = document.createElement('canvas');
  CSS.elementSources.set('fancy', bg);
</script>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the CSS Images Level 4 elementSources definition and the context from issues #3572 and #428. Determine whether elementSources and image() remain in scope, and whether the proposed maplike definition is appropriate; done requires a resolved specification direction from the CSS Working Group.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.