5 ms·
This is exactly the problem that these extensions intend to address: http://dev.chromium.org/developers/design-documents/extensions/apiwishlist http://dev.chro
by zzleeper 16y ago
This is exactly the problem that these extensions intend to address:
http://dev.chromium.org/developers/design-documents/extensions/apiwishlist http://dev.chromium.org/developers/design-documents/extensio...
- losvedir 16y agoAh, indeed. The Settings API mentioned on there is exactly what I'm looking for. I'm glad it's on their radar; hopefully, it can be implemented soon.
- zzleeper 16y agoMaybe this is what you looking for: http://code.google.com/chrome/extensions/trunk/contextMenus.html http://code.google.com/chrome/extensions/trunk/contextMenus.... =)
- Groxx 16y agoWhy is "Storage" in there? It does come for free via HTML5 APIs. It has for quite a while. Each extension has its own local storage, cookies (I think), and WebSQL database at its fingertips, even up to a few hundred megs if you request as much. Same with "Read-write user scripts" - those are content scripts, and I've used them in a couple extensions I've hacked out. The Chrome developers-wiki-thing is at times extremely out-dated (there were incorrect install instructions on one of the main dev-build pages for over a year), and I fear is mostly ignored. Don't trust everything on it.
- zzleeper 16y agoYou are right. I linked only to the _wishlist_ which is something not usually kept up-to-date. In the other page, there seems to be slightly more current information: http://dev.chromium.org/developers/design-documents/extensions http://dev.chromium.org/developers/design-documents/extensio...