Open
Bug 1941813
Opened 1 month ago
Updated 23 days ago
Include top-most frame of the stacktrace to all "log.entryAdded" events for Console API messages
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
NEW
People
(Reporter: whimboo, Unassigned)
References
(Blocks 2 open bugs, )
Details
(Whiteboard: [webdriver:m15])
With the landed changes on https://github.com/w3c/webdriver-bidi/pull/854 we should always include the stack trace for Console API messages.
|
Reporter | |
Comment 1•1 month ago
|
||
Tests will be downstream synced via bug 1942564.
Depends on: 1942564
|
|
Reporter | |
Comment 2•1 month ago
|
||
As a first step we could just try to only include the top-most frame of the stack, that we could extract more easily. Later on we could include the full stack once it's clear how much performance it will cost.
|
|
Reporter | |
Comment 3•23 days ago
|
||
Lets also file new bug for adding the full stack
Points: --- → 3
Flags: needinfo?(hskupin)
Priority: -- → P2
Whiteboard: [webdriver:blocked] → [webdriver:m15]
|
|
Reporter | |
Comment 4•23 days ago
|
||
Updating the summary to what we discussed last week. Also I filed bug 1944136 to include the full stack. For this bug we no longer need the work from bug 1744705.
No longer depends on: 1744705
Flags: needinfo?(hskupin)
Summary: "log.entryAdded" event should always include stacktrace for Console API messages → Include top-most frame of the stacktrace to all "log.entryAdded" events for Console API messages
You need to log in
before you can comment on or make changes to this bug.
Description
•