I'm sure someone has thought of this before but it occurred to me today that quite a few things people do in plugins could easily be done with user-supplied javascript files loaded into every page and it seems like it would be far far easier to implement than a full plugin architecture. For any other browser I probably wouldn't suggest this for performance reasons but Chromium solves that rather nicely.
The oft talked about flash blocker is a good example. Most flash on web sites these days is so badly coded it eats up CPU even when it's off-screen or minimized which makes having lots of tabs open a nightmare. A little js file loaded into every page before all the others and hooking the equivalent of DOMContentLoaded could easily traverse the DOM and remove unnecessary flash. Of course it wouldn't be as simple as just adding it at the top of the list of scripts to load since you'd have to avoid namespace conflicts. That'd mean somehow allowing the script to access the DOM without making it visible to the other scripts on the page. A private set of cookies would be beneficial, too, but would probably add more complexity. Ones that aren't sent to the site and can't be set by the site's javascript. Of course some script plugins might want access to the real cookies as well so maybe just a separate object for global script plugins functions. Just a thought, I hope it's not redundant. P6 --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
