[User reported] Click on tags in the log events rows to filter by those tags #9558

Activity

1. elliette

   added

   devtools-logging-screenIssues with the Logging screenIssues with the Logging screen

   P2important to work on, but not at the top of the work list.important to work on, but not at the top of the work list.

   cost: lowLow engineering cost to implement.Low engineering cost to implement.

   enhancement

   on Dec 2, 2025
2. elliette

   added

   contributions welcomeActively welcoming contributions for these high-priority issues.Actively welcoming contributions for these high-priority issues.

   on Mar 30, 2026
3. crackedhandle commented on Apr 20, 2026

   

   crackedhandle

   on Apr 20, 2026

   Contributor

   More actions

   Hi, I'd like to work on this issue. Is this still open for contributions?
4. kenzieschmoll commented on Apr 21, 2026

   

   kenzieschmoll

   on Apr 21, 2026

   Member

   More actions

   Yes, this is still open for contributions. One thing to be aware of: clicking the table row (outside of the tag) should still select the log even though clicking the tag will now apply a filter instead of selecting the log.
5. crackedhandle commented on Apr 22, 2026

   

   crackedhandle

   on Apr 22, 2026

   Contributor

   More actions

   Thanks for the clarification! I’ll make sure that clicking on the tag applies the filter, while clicking elsewhere on the row still selects the log. I am already working on this.
6. srawlins

   added

   type-enhancement

   and removed

   enhancement

   on Sep 29, 2026
7. nurullahturkoglu commented on Oct 10, 2026

   

   nurullahturkoglu

   on Oct 10, 2026

   More actions

   I'd like to pick this up, since #9802 and #9803 were closed as stale. My plan, following the review on #9803:

   • Each chip handles its own tap with an InkWell (with a null onTap for chips that can't filter, like the frame time chip), so tapping a chip applies a filter and tapping elsewhere on the row still selects the log.
   • The kind, isolate and zone chips set k:, i: and z: in the filter query. If the query already has that key, I'd replace its value and keep the rest, so tapping a kind chip and then an isolate chip gives k:stderr i:main.
   • There is no query argument for the log level, only the "minimum log level" setting. Should tapping the level chip set that setting to the chip's level, or would you prefer a new level: query argument?

   I'll add widget tests for each chip, a release note entry, and a GIF of the new behavior.