Ah I see, yes that is possible, my answer still stands. The chrome
extension will inject the Adobe script and call s.*, however, keep in
mind that if your chrome extension is going to run on sites that already
have Adobe install - public chrome extension, you may want to ensure you
implement a different S object so you don't overlap on an existing
implementation. As a matter of fact, you should do that regardless to be
on the safer side but everything else should work as normal.