Closed
Bug 1199002
Opened 9 years ago
Closed 9 years ago
Propagate JavaScript errors from executing script commands
Categories
(Remote Protocol :: Marionette, defect)
Remote Protocol
Marionette
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ato, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: pi-marionette-server)
When scripts are injected using Execute Script or Execute Async Script, we should catch any errors that are thrown and propagate them to the local end as "javascript error"’s.
Reporter | ||
Updated•9 years ago
|
Keywords: ateam-marionette-server
Updated•9 years ago
|
Blocks: fxos-dev-papercuts
Comment 1•9 years ago
|
||
What if that is an unrelated error as thrown by Firefox in a different component? Means how can we filter out errors as produced by the code in execute_(async_)script()?
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #1)
> What if that is an unrelated error as thrown by Firefox in a different
> component? Means how can we filter out errors as produced by the code in
> execute_(async_)script()?
I imagine we would wrap the code block that is injected. This isn’t a proposal for a content-wide window.onerror handler.
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•