Steps to replicate the issue (include links if applicable):
- See https://de.wikipedia.org/wiki/Benutzer_Diskussion:PerfektesChaos/js/lintHint#c-Bruce1ee-20240517171900-Qwerfjkl-20240517150600 for a link to a simple case, which is at https://en.wikipedia.org/w/index.php?oldid=1181833694
- Also see https://en.wikipedia.org/wiki/Wikipedia_talk:Linter#Milestone!! for a discussion that points to the back-end index location information that underlies this error
What happens?:
The interface that points to a specific location of a Linter error, for example any of the "edit" links at https://en.wikipedia.org/wiki/Special:LintErrors/stripped-tag?namespace=10 is supposed to jump the cursor in the editing window to the exact location of the Linter error, with the erroneous span or block of text or tag highlighted.
Instead, starting in October 2023 (see the first discussion linked above), the offsets started to be incorrect, overshooting the actual location of the error.
The problem appears to be present when multi-byte characters (or something like that; I don't know the technical details) are present. The location indexes do not appear to account for the size of those characters.
What should have happened instead?:
Any "edit" link on a Special:LintErrors page should jump to the exact location of the Linter error, as it did from 2018 until October 2023.
Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):
Other information (browser name/version, screenshots, etc.):