Closed Bug 1307924 Opened 8 years ago Closed 2 years ago

Handle tip-of-tree version of Chrome protocol

Categories

(DevTools :: Console, enhancement, P3)

Product:
DevTools
Component:
Console
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: linclark, Unassigned)

Details

(Whiteboard: [newconsole-reserve])

Originally posted by:linclark see https://github.com/devtools-html/gecko-dev/issues/217 There is a stable version of the Chrome protocol and a tip-of-tree version. `ConsoleMessage.parameters` have been [removed](https://github.com/ChromeDevTools/debugger-protocol-viewer/commit/acf8056789f0e1345fe9536f74f8a0a7ee174bbd#diff-22e7f1ed0925fad850e74056f3490040L1990) from tot and `ConsoleMessage.messageText` has been changed to `text`. The 2nd change isn't too much of an issue, but the first change has ramifications for our use of reps. If the server is not providing the RemoteObjects, then there's no need for something like reps on the client side.
Priority: -- → P2
Whiteboard: new-console
Blocks: enable-new-console
Flags: qe-verify-
Priority: P2 → P3
Whiteboard: new-console → [reserve-new-console]
Whiteboard: [reserve-new-console] → [reserve-console-html]
Priority: P3 → P4
Flags: qe-verify-
Priority: P4 → P2
Whiteboard: [reserve-console-html] → [newconsole-mvp]
Priority: P2 → P3
Whiteboard: [newconsole-mvp] → [newconsole-reserve]
Product: Firefox → DevTools
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.