1251139 - Support running a function in the parent with loadChromeScript

Status: RESOLVED FIXED

(Testing :: Mochitest, enhancement)

Description

[Matthew N. [:MattN]]

Sometimes you need to run different code in the parent for each test and creating a new .js file for use with loadChromeScript feels too heavyweight. The workaround is usually to use a data URI (like on mm.loadFrameScript) but that doesn't work with loadChromeScript since _readUrlAsString requires being able to do a sync open on the channel. It seems that isn't supported for data URIs and nsIChannel implementations aren't required to support that[1].

ContentTaskUtils supports providing a function (which will be stringified) to run in the content process and that seems to work well and is lighter-weight than a new file so it would be nice if loadChromeScript also supported loading functions.

[1] https://mxr.mozilla.org/mozilla-central/source/netwerk/base/nsIChannel.idl?rev=72b4f68bc170#147

Comment 1

[Matthew N. [:MattN]]

Attachment: MozReview Request: Bug 1251139 - Support running a function in the parent with loadChromeScript. r=ted

Review commit: https://reviewboard.mozilla.org/r/36517/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/36517/

Comment 2

[Joel Maher ( :jmaher ) (UTC -0800)]

https://reviewboard.mozilla.org/r/36517/#review34753

::: testing/specialpowers/content/SpecialPowersObserverAPI.js:464
(Diff revision 1)
> -                              { id: id, url: url, err: err, message: message,
> +                              { id, name: scriptName, err, message,

before we had a field named id, now we just pass in id without a name.

It appears we still reference aMessage.json.id, that indicates we have a named field id.

::: testing/specialpowers/content/specialpowersAPI.js:463
(Diff revision 1)
> +    let scriptArgs = { id };

here I think we are just sending in an id, not a named field.

Comment 3

[Matthew N. [:MattN]]

https://reviewboard.mozilla.org/r/36517/#review34753

> before we had a field named id, now we just pass in id without a name.
> 
> It appears we still reference aMessage.json.id, that indicates we have a named field id.

This is just new property syntax to avoid redundancy when the property name is the same as a local variable. `id: id,` is equivalent to `id,`

> here I think we are just sending in an id, not a named field.

Right, that's intentional. The name property is on the function object that gets added on in the block directly below.

Comment 4

[Matthew N. [:MattN]]

Comment on attachment 8723396 [details]
MozReview Request: Bug 1251139 - Support running a function in the parent with loadChromeScript. r=ted

Joel, did you see my reply?

Comment 5

[Joel Maher ( :jmaher ) (UTC -0800)]

Comment on attachment 8723396 [details]
MozReview Request: Bug 1251139 - Support running a function in the parent with loadChromeScript. r=ted

https://reviewboard.mozilla.org/r/36517/#review35555

thanks for clarifying the 'id'

Comment 6

[Pulsebot]

https://hg.mozilla.org/integration/fx-team/rev/a21e11fe4222

Comment 7

[Pulsebot]

https://hg.mozilla.org/integration/fx-team/rev/9643098c3d84

Comment 8

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/a21e11fe4222
https://hg.mozilla.org/mozilla-central/rev/9643098c3d84

Comment 9

[(not currently active) Ted Mielczarek]

Comment on attachment 8723396 [details]
MozReview Request: Bug 1251139 - Support running a function in the parent with loadChromeScript. r=ted

Apologies for not getting to this review in a timely manner.