[meta] DevTools working over Remote

RESOLVED FIXED in Firefox 33

Status

()

Firefox
Developer Tools
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jsantell, Assigned: vporof)

Tracking

unspecified
Firefox 33
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

A few tools do not work remotely currently. When using the canvas, shader, and audio tools within App Manager (connecting to Firefox OS simulator), errors such as below are thrown:

ShaderEditorPanel.prototype.open threw an exception: TypeError: this.conn.allocID is not a function

CanvasDebuggerPanel.prototype.open threw an exception: TypeError: this.conn.allocID is not a function

WebAudioEditorPanel open failed. undefined: this.conn.allocID is not a function panel.js:48
TypeError: gFront is undefined webaudioeditor.xul:1
(Reporter)

Updated

4 years ago
Depends on: 988928
(Reporter)

Updated

4 years ago
Depends on: 1019141
(Reporter)

Updated

4 years ago
Depends on: 1023529
(Assignee)

Comment 1

4 years ago
Seems there's just a single point of failure across all these tools.
I'll try on FxA tonight, as this could be from older version of Gecko on FFOS which doesn't have all the actors and features, but yeah, looks like the same issue across all similar tools
(Assignee)

Comment 3

4 years ago
Created attachment 8445706 [details] [diff] [review]
v
Assignee: nobody → vporof
Status: NEW → ASSIGNED
Attachment #8445706 - Flags: review?(jsantell)
This is no longer throwing weird errors! This fixes that problem and we can start checking out other RDP issues:

* Be able to hook into an Firefox OS's app on content creation without changing "pages" in the app-manager (all of these media tools miss that event)
* Debugging browser pages in Firefox OS (doesn't seem to pick up on events in iframes)
Comment on attachment 8445706 [details] [diff] [review]
v

Review of attachment 8445706 [details] [diff] [review]:
-----------------------------------------------------------------

Also, does framerateactor need to be exposed like this? Not sure how it works.
Attachment #8445706 - Flags: review?(jsantell) → review+
(Assignee)

Comment 6

4 years ago
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #5)
> 
> Also, does framerateactor need to be exposed like this? Not sure how it
> works.

Yes, it actually works \m/
(Assignee)

Comment 7

4 years ago
https://hg.mozilla.org/integration/fx-team/rev/85c88938e520
Whiteboard: [fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/85c88938e520
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 33
You need to log in before you can comment on or make changes to this bug.