element-shared should be replaced with element-scoped

Open Beginner friendly
#46,524 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
css
Domain
documentation

Research direction

The page source is files/en-us/web/css/reference/values/random/index.md, and the examples use element-shared where the reporter believes the keyword is element-scoped. Check the current CSS Values spec for the random() keyword, then search the file for element-shared and correct each occurrence. Done when the examples and prose match the spec and the page's own text describes element-scoped consistently.

Written by the indexing model from the issue text.

Description

Content:CSS needs triage
MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/random

What specific section or headline is this issue about?

element-scoped instead keeps width and height linked within each element, but gives each element its own value, so .a, .b, and .c become squares of different sizes:

What information was incorrect, unhelpful, or incomplete?

I could not find element-shared in the spec, I think element-scoped is the correct syntax
.a,
.b,
.c {
width: random(--custom-name element-shared, 10px, 200px);
height: random(--custom-name element-shared, 10px, 200px);
}

What did you expect to see?

.a,
.b,
.c {
width: random(--custom-name element-scoped, 10px, 200px);
height: random(--custom-name element-scoped, 10px, 200px);
}

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata
Page report details
Dominant language
Markdown
Stars
11.1k
Forks
23.3k
Avg merge
2d 14h
Merged PRs (30d)
165

Getting set up

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.

More from mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.