fix: ignore unmapped PerformanceIssue events#1852
Merged
Lightning00Blade merged 1 commit intoChromeDevTools:mainfrom Apr 17, 2026
Merged
Conversation
Lightning00Blade
approved these changes
Apr 16, 2026
Collaborator
Lightning00Blade
left a comment
Lightning00Blade
left a comment
There was a problem hiding this comment.
Thanks for the PR,
I think we can merge after the rebase and update to tests.
And remove the the hard coded bit after we update the version of devtools.
Signed-off-by: Asish Kumar <officialasishkumar@gmail.com>
officialasishkumar
force-pushed
the
fix/performance-issue-warning
branch
from
7bbfcee to
9808763
Compare
Lightning00Blade
approved these changes
Apr 16, 2026
Merged
via the queue into
ChromeDevTools:main
with commit Apr 17, 2026
ea57e86
28 of 30 checks passed
2 tasks
wolfib
pushed a commit
that referenced
this pull request
Apr 20, 2026
## Summary - ignore Audits `PerformanceIssue` events before passing them to the DevTools IssuesManager mapper, which currently has no handler for that issue code - preserve the existing mapper/logging path for other issue codes - add regression coverage that `PerformanceIssue` is ignored without collecting an issue or writing a console warning Fixes #1850 ## Testing - `npm run build` - `npm run test:no-build -- tests/PageCollector.test.ts` - `npm run check-format` Signed-off-by: Asish Kumar <officialasishkumar@gmail.com>
OrKoN
pushed a commit
that referenced
this pull request
Apr 21, 2026
🤖 I have created a release *beep* *boop* --- ## [0.22.0](chrome-devtools-mcp-v0.21.0...chrome-devtools-mcp-v0.22.0) (2026-04-21) ### 🎉 Features * add update notification to both binaries ([#1783](#1783)) ([e01e333](e01e333)) * auto handle dialogs during script evaluation ([#1839](#1839)) ([da33cb5](da33cb5)) * ensure extensions for file outputs ([#1867](#1867)) ([e7a0d50](e7a0d50)) * experimental click_at(x,y) tool ([#1788](#1788)) ([c4f5471](c4f5471)) * support Chrome extensions debugging ([#1922](#1922)) ([3ff21cf](3ff21cf)) * support DevTools header redactions as an option ([#1848](#1848)) ([5c398c4](5c398c4)) * **webmcp:** Add experimental tool to execute WebMCP tool ([#1873](#1873)) ([0aff266](0aff266)) * **webmcp:** Add experimental tool to list WebMCP tools page exposes ([#1845](#1845)) ([f97b573](f97b573)) ### 🛠️ Fixes * avoid showing update notification for local builds ([#1889](#1889)) ([3f0cf10](3f0cf10)), closes [#1886](#1886) * **cli:** correct WebP MIME type check in handleResponse ('webp' → 'image/webp') ([#1899](#1899)) ([e3a5f6b](e3a5f6b)), closes [#1898](#1898) * ignore unmapped PerformanceIssue events ([#1852](#1852)) ([ea57e86](ea57e86)) * **network:** trailing data in Network redirect chain ([#1880](#1880)) ([2f458c1](2f458c1)) * remove double space in navigate error message ([#1847](#1847)) ([429e0ca](429e0ca)) ### 📄 Documentation * clarify tools included into CLI ([#1925](#1925)) ([76ab9fa](76ab9fa)) * document network response and request extensions ([#1887](#1887)) ([796d6f2](796d6f2)) * fix skill and reference documentation issues ([#1249](#1249)) ([9236834](9236834)) * Include Mistral Vibe setup in README ([#1801](#1801)) ([582c9e0](582c9e0)) * Rename project and enhance README content ([#1856](#1856)) ([c066488](c066488)) * update the README on installing as a VS code agent plugin ([#1796](#1796)) ([1b5dcae](1b5dcae)) ### 🏗️ Refactor * move waitForEventsAfterAction to McpPage ([#1780](#1780)) ([c7c8f50](c7c8f50)) * use puppeteer Extension API ([#1911](#1911)) ([ec895f1](ec895f1)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PerformanceIssueevents before passing them to the DevTools IssuesManager mapper, which currently has no handler for that issue codePerformanceIssueis ignored without collecting an issue or writing a console warningFixes #1850
Testing
npm run buildnpm run test:no-build -- tests/PageCollector.test.tsnpm run check-format