Is Blink>Javascript the right component for this? There is no action for the Blink team it seems.

Also, not sure if flagging all usage of replace() to use /g is a good solution. There can be legitimate usages of replace() to only replace the 1st occurrence.

Demanding unit tests for the code that uses replace(), during code review seems more scaleable I think.

dpapad@ discussed this further offline.

The goal is to have something automated that advises SWEs about the potential to misunderstand .replace(). That doesn't have to be a linter test, but it needs to be more than having SWEs simply "do better", since the code did have unit tests that didn't cover that case (and the code and unit tests were reviewed by *very* experienced JavaScript SWEs).

We also discussed whether expecting replace() to replace all occurrences would be a common case. I found that searching for why: javascript replace() only replaces the first instance, finds several help forum Q&As. There are 100's of combined upvotes on answers explaining this unexpected behavior. Certainly more research can be done, but there does seem to be an issue here.

This is a not a PM-goal (as I initially thought it would be), so lessening the pri.

Archiving P3s older than 1 year with no owner or component.