Closed
Bug 1472670
Opened 6 years ago
Closed 6 years ago
Convert TabActor events to Protocol.js
Categories
(DevTools :: General, enhancement, P2)
DevTools
General
Tracking
(firefox63 fixed)
RESOLVED
FIXED
Firefox 63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: yulia, Assigned: yulia)
References
Details
Attachments
(1 file)
The tab actor events were not updated to protocol.js. Protocol.js has its own way of handling events and we should use that instead
Comment hidden (mozreview-request) |
Comment 2•6 years ago
|
||
mozreview-review |
Comment on attachment 8989703 [details]
Bug 1472670 - use Protocol.js events instead of this.conn.send;
https://reviewboard.mozilla.org/r/254718/#review261586
Code analysis found 1 defect in this patch:
- 1 defect found by mozlint
You can run this analysis locally with:
- `./mach lint path/to/file` (JS/Python)
If you see a problem in this automated review, please report it here: http://bit.ly/2y9N9Vx
::: devtools/shared/specs/targets/browsing-context.js:135
(Diff revision 1)
> + },
> + frameUpdate: {
> + type: "frameUpdate",
> + frames: Option(0, "nullable:array:browsingContextTarget.window"),
> + selected: Option(0, "nullable:number")
> + destroyAll: Option(0, "nullable:boolean")
Error: Parsing error: unexpected token destroyall [eslint]
Comment hidden (mozreview-request) |
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → ystartsev
Comment hidden (mozreview-request) |
Assignee | ||
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
mozreview-review |
Comment on attachment 8989703 [details]
Bug 1472670 - use Protocol.js events instead of this.conn.send;
https://reviewboard.mozilla.org/r/254718/#review261626
Thanks, it looks good.
It would be great to push to DAMP before merging as I know that protocol.js events can be slow depending on the types... I had to workaround that for netmonitor actor.
::: devtools/client/debugger/new/src/client/firefox/events.js:104
(Diff revision 3)
> paused,
> resumed,
> newSource
> };
> exports.setupEvents = setupEvents;
> exports.clientEvents = clientEvents;
It is not very clear why this file appear on mozreview, it doesn't show any particular difference?
::: devtools/shared/specs/targets/browsing-context.js:59
(Diff revision 3)
> + url: "string",
> + title: "string",
> + nativeConsoleAPI: "boolean",
> + state: "string",
> + isFrameSwitching: "boolean"
> +});
This is unused.
Attachment #8989703 -
Flags: review?(poirot.alex) → review+
Comment hidden (mozreview-request) |
Assignee | ||
Comment 8•6 years ago
|
||
Assignee | ||
Comment 9•6 years ago
|
||
Updated•6 years ago
|
Severity: normal → enhancement
Priority: -- → P2
Comment 10•6 years ago
|
||
Pushed by ystartsev@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fa92a04dda3d
use Protocol.js events instead of this.conn.send; r=ochameau
Comment 11•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
You need to log in
before you can comment on or make changes to this bug.
Description
•