Re: [crx] Custom Manifest Entries

[Aaron Boodman]

On Wed, Aug 1, 2012 at 6:06 PM, Mihai Danila <viri...@gmail.com> wrote:
> Hey, are there any plans to keep the ability to have custom entries in
> Chrome extension manifests? Some of my extensions include custom data which
> I've been hosting in the manifest (based on the observation that the
> manifest can be loaded just like any other resource). Is it possible to
> continue to allow custom sections without the warnings currently in Chrome
> 21, perhaps in a dedicated top level section, such as "custom_data"?
>
> This will inform my refactoring for supporting manifest version 2.

We can't really support this because any future entries we add to the
manifest could collide with custom things you added.

Why not just have your static data in a JavaScript file? It's easier
to get out than the manifest - just include the script file. Or if you
like manifests for some reason, you could add your own manifest, and
fetch it with XHR, then parse it with JSON.

- a

[Mike West]

Hi Mihai,

Sounds reasonable to me. Would you mind filing a feature request at http://new.crbug.com/ and posting the bug ID?

Thanks!

-mike

[Tony Sukiennik]

I solved this problem by including my own Settings.json file in my project and then simply loading it on .ready in the background page…   You’ll need to do something like this even if you bug/feature gets addressed given the Chrome Version cycle time…   I’d be glad to give you some code snippets…

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/-/BMOzVlpZDOMJ.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

[Mihai Danila]

I have submitted a bug report as suggested by Mike. The conflict issue can be mitigated by dedicating a special section to custom data. Just something for you guys to ponder. In the past, I chose the manifest as the host for custom configuration because if I ever needed standard manifest configuration in addition to custom configuration I could load it in one shot. Also, it felt like extending the manifest to serve the purpose of the extension and providing a single configuration was the natural thing to do. Also, fewer files to edit (one extension is a barebones workflow automator used at work and a new workflow would typically require edits to the URLs where stuff was to be injected. I didn't want to inject programmatically because then I would have to request wider permissions which I felt could constitute a barrier to adoption for colleagues.)

As I said, not a biggie. The feature request is in, feel free to disregard.

[Jeremy Daley]

A code snippets would be great. Thank you!

To unsubscribe from this group, send email to chromium-extensions+unsub...@chromium.org.