Hi PAEz, I'm a little confused about your answer..... sorry I need to ask.
Do you think it's great that access to such images through the Omnibox should be disabled, as brought forth by k.thirukumaran, or do you think it's great that we are able to access them? Accessing an extension's manifest.json through chrome-extension:// extension_id/manifest.json through the Omnibox just opens a Save As dialog popup for me. What good is that? I've already got the extension installed, including the manifest.json. I don't need to save it again.... On Dec 15, 5:57 am, PAEz <[email protected]> wrote: > I think its great, if only we could access the manifest.json that way > aswell ;) > > On Dec 15, 8:26 pm, krtulmay <[email protected]> wrote: > > > > > Do you mean as opposed to the only slightly more difficult method of > > opening a file browser to > > > ...\User Data\Default\Extensions\<directory of theme>.... > > > and accessing the copyrighted images directly? > > > After all, all of a theme's image elements are listed in the > > Preferences file and are all accessible through the Omnibox. > > > On Dec 15, 12:45 am, "[email protected]" > > > <[email protected]> wrote: > > > I found this when I was trying to access the code of ntp, paste the > > > following in chrome omnibox > > > > chrome://theme/theme_ntp_background > > > > you'll see the background image of the currnet theme , similarly you > > > can type in theme_toolbar or theme_ntp_attribution (all image > > > elements) they all showup - now is this going to be a problem for > > > copyrighted themes? should it be disabled? -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
