mdn / mdn/browser-compat-data

javascript.builtins.String.substr - No spec level deprecation

Open
#29,608 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

javascript p3
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

BCD says it's deprecated (kinda?) and MDN uses it to say:

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

That's too broad definition of "deprecated". This specific function cannot be removed as doing so will cause a major webcompat harm, and I don't see plan from any browser vendors to do so, nor the spec says it's deprecated. We should not imply that it may be removed soon.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

Unmark it, or maybe make two levels of deprecation - "not recommended" vs "being actually removed".

But then I think the latter will be removed completely from MDN with the modern policy, right?

Did you test this? If so, how?

(N/A)

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/substr

MDN metadata
MDN page report details
  • Query: javascript.builtins.String.substr
  • Report started: 2026-05-05T14:44:05.495Z

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

Locate the BCD entry for javascript.builtins.String.substr and compare its deprecation data with the linked ECMAScript specification and MDN page. Clarify with maintainers whether the entry should be unmarked or whether BCD needs a separate deprecation distinction. Done means the chosen policy is reflected consistently in the data and its MDN interpretation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.