No, really nothing. In last version I only add two more permissions
(webRequest and webRequestBlocking) and add listener on
beforeSendHeaders, which only adds one header to request.
chrome.webRequest.onBeforeSendHeaders.addListener(function(details){
if (details.url.match(/<***>/)){
details.requestHeaders.splice(1,0,{name: "Referer", value:
"<***>"});
}
return {requestHeaders: details.requestHeaders};
},{
urls: ["http://<***>/*", "http://<***>/*"]
},[
"blocking",
"requestHeaders"
]);
On 20 Тра, 11:55, PhistucK <
phist...@gmail.com> wrote:
> Did you happen to include a DLL file (or SO, or DynLib) within your
> extension?
> Do you have any <embed> or <object> within your HTML code (or JavaScript
> created ones)?
>
> ☆*PhistucK*
>
>
>
>
>
>
>
> On Sun, May 20, 2012 at 10:47 AM, uzer <
uzer2...@gmail.com> wrote:
> > My chrome extension is still in pending review status because
> > something related to NPAPI, since 05/16/2012.
> > I'm not sure, my extension really uses this API.
> > What's the problem and how long should I wait? Does this now will
> > appear after each extension update?
> > I can't make any changes, and users are waiting for a new version.
>
> > Exntension ID is: mjcfgnfpobiaemefgolkijjffmepckpc
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Chromium Apps" group.
> > To post to this group, send email to
chromium-a...@chromium.org.
> > To unsubscribe from this group, send email to
> >
chromium-apps+unsubscr...@chromium.org.