You weren't totally on point but you shed some very needed light. I thought that it was easier and more secure to use the internal page, but you're saying it's actually not.
In any case, it's not a problem because the latest trunk build remembers the last theme you had installed. I guess it shouldn't be too hard then to pass that info onto the gallery page and keep everything online. On Aug 12, 1:41 am, PhistucK <[email protected]> wrote: > I have not read through the entire message, so forgive me if I am saying > something unrelated and that was already answered here -It seems like there > might be security issues with loading web resources in the internal pages, > since internal pages seem to have a lot of power and privileges and the web > is posed here as "unsafe and must be sandboxed through the whole way" (which > is correct, of course). Combining the two may lead to unfortunate > consequences. > For the same reason, the "Tips & Recommendations" was pulled out. > There is a command line switch called --enable-web-resources and, probably, > just like the remote fonts feature (which is preventing Chrome from fully > passing the ACID3 test, as far as I recall), that is behind a command line > switch due to yet to be resolved security concerns. > > ☆PhistucK > > > > On Wed, Aug 12, 2009 at 07:08, Meok <[email protected]> wrote: > > > I'm all in favor of Chromium using web interfaces instead of local > > code. As I've said before in a thread on Chromium-Discuss, if Google > > is creating a browser to maximize the potential of the web, and > > encourage web developers to make more complex applications, then the > > said Google browser should be leading the charge by embracing the web > > as a platform. If you're going to invest so much in V8 to make AJAX > > faster, why not use AJAX and an online interface to do many things for > > the browser itself? > > > I'm in favor of seeing Bookmarks and Themes presented in "Web-app" > > format, running powerful Javascript on par with Gmail or Google Docs, > > with effects as stunning as some of the ChromeExperiements. In other > > words, show off what the browser can do, as well as promote the use of > > the web as a platform. > > > However, the reason I'm a little skeptical is that I'm afraid Google > > may come under fire. How will the Theme Gallery know my most used > > themes without authentication. If you make the theme gallery pull the > > info from the browser history, you may be accused of violating privacy > > rights, and if you force users to sign-in to the gallery to access the > > feature, you make the process more tedious and if you use a Google > > account, you risk looking monopolistic. Maybe I'm just being too > > paranoid, and maybe you already have an ingenious programming > > solution, but that was my motivation for suggesting the internal > > page. > > > On Aug 11, 9:23 pm, Peter Kasting <[email protected]> wrote: > > > On Tue, Aug 11, 2009 at 4:03 PM, Meok <[email protected]> wrote: > > > > Just to add my two cents worth. Even though there is a full resource, > > > > I still see a need for users to be able to keep their favorites easily > > > > accessible. It;s the same philosophy of having a New Tab Page even > > > > though you can pull back your most visited sites from the bookmarks. > > > > As we've already (sort of) said on this thread, it seems like having your > > > MRU themes is useful, but it's appropriate to do as an element of the > > theme > > > gallery itself, not as a separate local page. > > > > PK --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
