Linked by Thom Holwerda on Thu 23rd Sep 2010 21:36 UTC, submitted by google_ninja
Thread beginning with comment 442483
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
So what you're saying is, there are limitations on the hooks into Chrome which would impact other "Firefox Add-ins"?
Is this just an AdBlock issue or a general extensibility issue with Chrome?
Is this just an AdBlock issue or a general extensibility issue with Chrome?
According to the author of AdBlock for Chrome, it is a Chrome issue only.
https://chrome.google.com/extensions/detail/gighmmpiobklfepjocnamgkk...
Webkit in Safari apparently does not suffer the same issue.
http://code.google.com/p/chromium/issues/detail?id=35897#c63
A partial solution to this problem is now available. Chrome now contains an event accessible to content scripts called "beforeload".
"beforeload" is a partial solution only in Chrome, apparently some percentage of "loads" still occur only in Chrome.





Member since:
2005-12-15
So what you're saying is, there are limitations on the hooks into Chrome which would impact other "Firefox Add-ins"?
Is this just an AdBlock issue or a general extensibility issue with Chrome?