chrome.tabs.executeScript on a specific frame

[Ilan]

Hi,

I'm using chrome.tabs.executeScript, and support chrome version 45+.

From what I recall when I checked (about a year ago) - it wasn't possible to supply a frameId, so I resorted to inject my script to all frames.

From what I see now, the optional frameId is available from chrome 39 (https://developer.chrome.com/extensions/tabs#method-executeScript)

However, I want to make sure that this is indeed the case (and not a typo in the documentation). 

I tried to look in the release notes, but didn't find anything.

Can anyone point me to the release notes in which this feature was added?

Thanks!

Ilan

[Antony Sargent]

Looks like that was added by https://codereview.chromium.org/1628423002 which landed as git commit c872b368db45bc6d2f2bd9a4b7a0eb2ce8d

I don't think it was specifically called out in release notes, so you might have to do some leg work to figure out exactly when it became available.

https://omahaproxy.appspot.com/ has some tools towards the bottom that can help with this. 

Also possibly helpful:

http://googlechromereleases.blogspot.com/

https://en.wikipedia.org/wiki/Google_Chrome_release_history

--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at https://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/78c6755d-4736-4a09-9f2c-f96248dc0103%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Devlin Cronin]

Given revision c872b368db45bc6d2f2bd9a4b7a0eb2ce8d, you can check https://chromium.googlesource.com/chromium/src/+/52277c872b368db45bc6d2f2bd9a4b7a0eb2ce8d/chrome/VERSION to find that this was added in Chrome 50.

Cheers,

- Devlin

On Thursday, May 26, 2016 at 11:23:36 AM UTC-7, Antony Sargent wrote:

Looks like that was added by https://codereview.chromium.org/1628423002 which landed as git commit c872b368db45bc6d2f2bd9a4b7a0eb2ce8d

I don't think it was specifically called out in release notes, so you might have to do some leg work to figure out exactly when it became available.

https://omahaproxy.appspot.com/ has some tools towards the bottom that can help with this. 

Also possibly helpful:

http://googlechromereleases.blogspot.com/

https://en.wikipedia.org/wiki/Google_Chrome_release_history

On Thu, May 26, 2016 at 5:45 AM, Ilan <il...@testim.io> wrote:

Hi,

I'm using chrome.tabs.executeScript, and support chrome version 45+.

From what I recall when I checked (about a year ago) - it wasn't possible to supply a frameId, so I resorted to inject my script to all frames.

From what I see now, the optional frameId is available from chrome 39 (https://developer.chrome.com/extensions/tabs#method-executeScript)

However, I want to make sure that this is indeed the case (and not a typo in the documentation). 

I tried to look in the release notes, but didn't find anything.

Can anyone point me to the release notes in which this feature was added?

Thanks!

Ilan

--
You received this message because you are subscribed to the Google Groups "Chromium-Extensions-Announce" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
To post to this group, send email to chromium-extensions@chromium.org.