I was able to write to DOM of a downloaded page from my toolstrip or background page. (Actually I still can in dev channel, except for some warnings). The new build stops this trick from working. (I notice it in 25314, though it could have started in an earlier build). I got "Unsafe JavaScript attempt to access frame with URL ... Domains, protocols and ports must match." Is there a work-around? I was able to modify DOM from toolstrip because the new URL is opened in toolstrip using var wnd = window.open(...) This way I have the wnd object and access to DOM of the downloaded page. It's arguably reasonable since the extension opened the new page. If I have work-around (say do this in content script), why couldn't I do it in toolstrip? I don't want to use content_script. My extension is pretty complicated, I already have a content_script (matching *) to gather information and send it to the toolstrip. The toolstrip then opens a new window with content from my server, and inject the gathered information into the DOM of downloaded page. Adding another content script for the downloaded page sounds not clean to me, and the server URL may change. I won't do it unless I have no choice... Thanks in advance,
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
