mdn / mdn/fred

Inconsistent use of language names - JS / JavaScript / JAVASCRIPT

Open
#984 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
233
Forks
61
Avg merge
1d 1h
Merged PRs (30d)
82

Description

Summary

Note: This issue is from https://github.com/orgs/mdn/discussions/426.

Live samples show abbreviated language names like JS and MD in live samples' headers, e.g. setTimeout(). However, showing the full names makes it more friendly to beginners and enables the removal proposed in https://github.com/orgs/mdn/discussions/426.

URL

https://developer.mozilla.org/en-US/docs/Web/API/setTimeout#syntax

Reproduction steps
  1. Navigate to the linked page above.
  2. Look at the header in the live sample.
Expected behavior

Seeing "JavaScript".

Actual behavior

Seeing "JS".

Device

Desktop

Browser

Firefox

Browser version

Stable

Operating system

Windows

Screenshot

No response

Anything else?

The normative advisement in CSS Text implies that it's incorrect to use text-transform for these headers. This already shows symptoms in this MDN page with WebIDL codes.

Validations

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 at the linked setTimeout() page and inspect how the live sample header labels its language. Trace that label to the frontend source, then check other live samples for the same naming behavior. Done means the header displays “JavaScript” rather than “JS” without relying on text transformation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.