Closed Bug 1861309 Opened 11 months ago Closed 11 months ago

Use 1-origin column number in Module APIs and internal objects

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED FIXED
121 Branch
Tracking Status
firefox121 --- fixed

People

(Reporter: arai, Assigned: arai)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

https://searchfox.org/mozilla-central/search?q=ColumnNumberZero&path=Module&case=false&regexp=false

Module-related API and objects use 0-origin column number, but they're for error reporting, which is already using 1-origin column number.

Summary: Use 1-origin column number in modules → Use 1-origin column number in Module APIs and internal objects
Summary: Use 1-origin column number in Module APIs and internal objects → Use 1-origin column number in modules
Summary: Use 1-origin column number in modules → Use 1-origin column number in Module APIs and internal objects
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Pushed by arai_a@mac.com: https://hg.mozilla.org/integration/autoland/rev/39474a3e2d59 Part 1: Use 1-origin column number in JS::GetRequestedModuleSourcePos and ModuleLoaderBase::HandleResolveFailure. r=jonco https://hg.mozilla.org/integration/autoland/rev/bf25e4eb7faa Part 2: Use 1-origin column number in module stencils and ThrowResolutionError. r=jonco
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: