Skip to content

fix: use 1-based line/column and fix wasm offsets in stack frames#884

Merged
OrKoN merged 1 commit intomainfrom
use-ui-location-link-text
Feb 4, 2026
Merged

fix: use 1-based line/column and fix wasm offsets in stack frames#884
OrKoN merged 1 commit intomainfrom
use-ui-location-link-text

Conversation

@szuend
Copy link
Contributor

@szuend szuend commented Feb 4, 2026

UILocation.linkText does the right thing when formatting a location, e.g. a wasm location will be formatted as foo.wasm:0x95.

@szuend szuend force-pushed the use-ui-location-link-text branch from 51ba75a to fad6bf8 Compare February 4, 2026 07:28
@szuend szuend force-pushed the use-ui-location-link-text branch from fad6bf8 to 35cc9d5 Compare February 4, 2026 08:00
@szuend szuend force-pushed the use-ui-location-link-text branch from 35cc9d5 to 0c27151 Compare February 4, 2026 08:00
@OrKoN OrKoN enabled auto-merge February 4, 2026 08:02
@szuend szuend requested a review from OrKoN February 4, 2026 08:11
@OrKoN OrKoN added this pull request to the merge queue Feb 4, 2026
Merged via the queue into main with commit 7e1ec81 Feb 4, 2026
31 of 33 checks passed
@OrKoN OrKoN deleted the use-ui-location-link-text branch February 4, 2026 08:19
github-merge-queue bot pushed a commit that referenced this pull request Feb 4, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.16.0](chrome-devtools-mcp-v0.15.1...chrome-devtools-mcp-v0.16.0)
(2026-02-04)


### 🎉 Features

* include source-mapped stack trace for uncaught errors
([#876](#876))
([ecef712](ecef712))


### 🛠️ Fixes

* accidental extra typing in the fill tool
([#886](#886))
([3d6e59d](3d6e59d))
* update evaluateScript description formatting
([#880](#880))
([24db9dd](24db9dd))
* use 1-based line/column and fix wasm offsets in stack frames
([#884](#884))
([7e1ec81](7e1ec81))


### 📄 Documentation

* mention source-mapped stack traces in 'Key features'
([#883](#883))
([579d18a](579d18a))
* remove outdated --channel=beta note
([#882](#882))
([acdb5c9](acdb5c9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
…romeDevTools#884)

`UILocation.linkText` does the right thing when formatting a location,
e.g. a wasm location will be formatted as `foo.wasm:0x95`.
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.16.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.15.1...chrome-devtools-mcp-v0.16.0)
(2026-02-04)


### 🎉 Features

* include source-mapped stack trace for uncaught errors
([ChromeDevTools#876](ChromeDevTools#876))
([ecef712](ChromeDevTools@ecef712))


### 🛠️ Fixes

* accidental extra typing in the fill tool
([ChromeDevTools#886](ChromeDevTools#886))
([3d6e59d](ChromeDevTools@3d6e59d))
* update evaluateScript description formatting
([ChromeDevTools#880](ChromeDevTools#880))
([24db9dd](ChromeDevTools@24db9dd))
* use 1-based line/column and fix wasm offsets in stack frames
([ChromeDevTools#884](ChromeDevTools#884))
([7e1ec81](ChromeDevTools@7e1ec81))


### 📄 Documentation

* mention source-mapped stack traces in 'Key features'
([ChromeDevTools#883](ChromeDevTools#883))
([579d18a](ChromeDevTools@579d18a))
* remove outdated --channel=beta note
([ChromeDevTools#882](ChromeDevTools#882))
([acdb5c9](ChromeDevTools@acdb5c9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants