Closed
Bug 1023525
Opened 10 years ago
Closed 10 years ago
[meta] DevTools working over Remote
Categories
(DevTools :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 33
People
(Reporter: jsantell, Assigned: vporof)
References
Details
(Keywords: meta)
Attachments
(1 file)
3.96 KB,
patch
|
jsantell
:
review+
|
Details | Diff | Splinter Review |
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
Assignee | ||
Comment 1•10 years ago
|
||
Seems there's just a single point of failure across all these tools.
Reporter | ||
Comment 2•10 years ago
|
||
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•10 years ago
|
||
Reporter | ||
Comment 4•10 years ago
|
||
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)
Reporter | ||
Comment 5•10 years ago
|
||
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•10 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•10 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
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 33
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•