Thank you very much Nicolas. This trick is exactly what I was looking for. It's fine for me. It's still nice for next version to have all these paramters editable from the GUI. Chrome is truly a good challenger. :)
Fulgore On 22 sep, 07:56, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote: > On Sun, Sep 21, 2008 at 10:39 PM, <[EMAIL PROTECTED]> wrote: > > > Thanks Nicolas for your answer. > > You're absolutly right, put each time I click on a external protocol > > link I have security popup... > > In fact I did this special request because I've made a web application > > based on this for my work. Using it, it's really uncomfortable with > > Chrome to validate each time the same link. It seems IE isn't doing > > any check and allow anything without asking. > > On the other hand, Firefox display a popup for a each new protocol but > > you can check the mark "remember my choice for all link of this type". > > A similar improvement would be the best for my problem. > > Having an option to "remember my choice" is a feature that we want to > implement. The code was designed to do this, but we don't have a good way > yet to display the preferences to the user so he can change his mind. > > If you have a given protocol that you want to open on your own machine > without warning, and don't mind hacking around, open your "Local State" file > in %userprofile%\local settings\application data\google\chrome\User Data. > (Assuming you are on windows xp) and search for "protocol_handler". Set > your protocol to "false". > > Nicolas > > > > > Thanks, > > > On 18 sep, 17:15, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > At this point chrome does not support launching externalprotocolfrom > > > the omnibox (address bar). > > > > On the other hand, if you click on a link on a webpage pointing to an > > > externalprotocolhandler, it will work. > > > > Alternatively, you can also create a bookmark pointing to an > > externalprotocolhandler. > > > > But the really cool thing that you can also do (which is sort of a > > > hack), is to add a new search engine to the omnibox for that. > > > > - Right click the omnibox and select "Edit search engines" > > > - Click the "Add" button > > > - Set the name to "vnc" and the keyword to "vnc" > > > - Set the URL to "vnc:%s" > > > > And now when you want to connect to vnc on port 127.0.0.1, just type > > > vnc[tab]127.0.0.1 > > > > I hope this helps > > > > Nicolas > > > > On 9/18/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > > This is a firefox and IE feature but I wasn't able to find it in > > > > Chrome. > > > > ProtocolHandler allow to manageprotocolnot supported by the > > > > browser. > > > > Typically on windows or mac, you can type telnet:127.0.0.1 on your > > > > > browser or windows, and the browser will launch your default telnet > > > > > client (on windows, this is defined on registry). > > > > > This allow also to customize association and manage customprotocol > > > > > (like type vnc:127.0.0.1 to start vnc). > > > > > It could be great if Chrome support this interesting feature > > > > especially for Web based application. > > > > > Kind regards, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
