deg909 wrote:If so, could XSS protection be implemented for Chrome without threatening Google funding?
Giorgio Maone wrote:Yes, the API for extensions is not complete yet, but I've been already contacted by the Google Chrome engineers who are trying to close this gap, because they really want both NoScript and FlashGot on Chrome.
new_kid wrote:Is it the same API that is needed for NoScript that is required before FlashGot will be available for Chrome? (sorry if this question should be asked in the flashgot development section, but i figured since you mentioned it here, i'd ask here)
Giorgio Maone wrote:I'm in contact with Adam Barth, Peter Kasting and other Chrome developers in order to make it happen, but "soon" is not exactly the word.
Vux wrote:Does that mean it will now be possible, but may take a while? Or that it's still a question of IF it's even possible on Chrome?
Giorgio Maone wrote:Vux wrote:Does that mean it will now be possible, but may take a while? Or that it's still a question of IF it's even possible on Chrome?
It means the the technology infrastructure to make it possible is not there yet (so "now be possible" does not makes much sense), but I'm in talks with good will Google people who say they want it to happen.
On the other hand, many months ago I had been contacted for the same reason by Google people who said they wanted it to happen, so I can't commit to any date or give the whole thing for sure.
Giorgio Maone wrote:Last week I've been told by some Google folks that Chrome devs want to improve usability of their script-blocking UI and to speed-up the development of their long languishing "privacy blocklist API", which would allow some but not all of the NoScript functionality to be implemented in extensions.
Anyway the same sources confirmed that a more powerful network-hooking API (like the ones available on Mozilla's Gecko and used by the most advanced NoScript features) is not planned.
Giorgio Maone wrote:Last week I've been told by some Google folks that Chrome devs want to improve usability of their script-blocking UI and to speed-up the development of their long languishing "privacy blocklist API", which would allow some but not all of the NoScript functionality to be implemented in extensions.
Anyway the same sources confirmed that a more powerful network-hooking API (like the ones available on Mozilla's Gecko and used by the most advanced NoScript features) is not planned.
Return to NoScript Development
Users browsing this forum: No registered users and 6 guests