Use 1-based column number in custom formatter
Categories
(DevTools :: Debugger, task)
Tracking
(Not tracked)
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(2 obsolete files)
nsIScriptError
has been using a mix of 0-based and 1-based column number.
Custom formatter had been using 0-based column number for nsIScriptError
.
function logCustomFormatterError(window, errorMsg, script) {
...
const { url, source, startLine, startColumn } = script ?? {};
...
scriptError.initWithWindowID(
`Custom formatter failed: ${errorMsg}`,
url,
source,
startLine,
startColumn,
bug 1862693 changes the Debugger API to use 1-based column number, while keeping the consumer to use 0-based.
bug 1864168 patches are going to modify other nsIScriptError
consumers to use 1-based column number,
so it would be nice to align with it.
Comment 1•10 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Assignee | ||
Comment 2•10 months ago
|
||
Assignee | ||
Comment 3•10 months ago
|
||
Depends on D193980
Comment 4•10 months ago
|
||
Comment on attachment 9364281 [details]
Bug 1864783 - Use 1-based column number in tracer and DevToolsStartup command line handling. r?ochameau!
Revision D193981 was moved to bug 1865005. Setting attachment 9364281 [details] to obsolete.
Updated•10 months ago
|
Assignee | ||
Comment 5•10 months ago
|
||
Given this doesn't block bug 1862693 change, the patch will be folded into bug 1862693 patch.
Description
•