[chromium-dev] Re: Kiosk Mode for Chrome
Most kiosk applications I have developed never leave their designated pages anyway. There are no 'offsite' links or anything. Thus the content is fully controlled. Downloads would not have to be disabled for me. The only 2 key options I would personally want for a kiosk mode, are fullscreen (not maximized, literally fullscreen) launching from commandline, and no status bubble on links and such. Almost all other things I need adjusted (such as context menu and such) can be handled easily with javascript. On Sep 25, 7:32 am, Adam Barth aba...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.org wrote: Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? We could also turn off other features that don't make sense for kiosks, like downloading files. Adam --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
Peter is giving excellent comments, and he raised an important question regarding what makes me decide what gets blocked. I have some questions to ask the group and others who are interested. What would you want Kiosk to block? I am currently trying to block the following areas: - Save page (should I block this) - Open new page - Open tabs - Open Incognito windows - Print page (should I block this) - Browser Exits (except ALT+F4) - Copy Links/Images (should I block this) - Status bar - Fullscreen popup - Popups (should I block this) Any comments regarding the above? -Mohamed On Fri, Sep 25, 2009 at 1:51 PM, Jeremy Orlow jor...@chromium.org wrote: No objections. I think it's a good idea, you're not the only one who wants this, and it seems like it can be done very cleanly. On Fri, Sep 25, 2009 at 10:47 AM, Adam Barth aba...@chromium.org wrote: On Fri, Sep 25, 2009 at 10:43 AM, Mohamed Mansour m...@chromium.org wrote: I could submit a cleaner patch (which does it right) that introduces Kiosk mode for Chrome. Are there any objections? None from me. :) Adam --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Tue, Sep 29, 2009 at 4:15 PM, Jeremy Orlow jor...@chromium.org wrote: I'm guessing different people/companies will have different needs for a kiosk mode. Maybe all of these should be separate flags rather than one kiosk flag? We could then offer recommendations in a Chromium for kiosks Wiki page? I think the reasoning for allowing this feature is that some minority would find it helpful and it wouldn't hurt much. I'm concerned that it is getting much too complicated. I think we shouldn't do it if it is going to be this complicated. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Tue, Sep 29, 2009 at 4:20 PM, Brett Wilson bre...@chromium.org wrote: On Tue, Sep 29, 2009 at 4:15 PM, Jeremy Orlow jor...@chromium.org wrote: I'm guessing different people/companies will have different needs for a kiosk mode. Maybe all of these should be separate flags rather than one kiosk flag? We could then offer recommendations in a Chromium for kiosks Wiki page? I think the reasoning for allowing this feature is that some minority would find it helpful and it wouldn't hurt much. I'm concerned that it is getting much too complicated. I think we shouldn't do it if it is going to be this complicated. Would multiple command line flags rather than one really complicate the design? Mohamed's original patch was just a bunch of if statements keying off of one flag. Seems like the same amount of work to have each if statement key off of a different one. Or am I missing something? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Tue, Sep 29, 2009 at 4:37 PM, Jeremy Orlow jor...@chromium.org wrote: On Tue, Sep 29, 2009 at 4:20 PM, Brett Wilson bre...@chromium.org wrote: On Tue, Sep 29, 2009 at 4:15 PM, Jeremy Orlow jor...@chromium.org wrote: I'm guessing different people/companies will have different needs for a kiosk mode. Maybe all of these should be separate flags rather than one kiosk flag? We could then offer recommendations in a Chromium for kiosks Wiki page? I think the reasoning for allowing this feature is that some minority would find it helpful and it wouldn't hurt much. I'm concerned that it is getting much too complicated. I think we shouldn't do it if it is going to be this complicated. Would multiple command line flags rather than one really complicate the design? Mohamed's original patch was just a bunch of if statements keying off of one flag. Seems like the same amount of work to have each if statement key off of a different one. Or am I missing something? The original patch was billed as let's make full screen a command line switch which people were generally OK with. This proposal touches a dozen subsystems for an unofficially supported feature, whether it's with different command line switches or not. If it's this complicated, it needs to be designed cleanly, tested, and with official support. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Tue, Sep 29, 2009 at 04:37:46PM -0700, Jeremy Orlow wrote: On Tue, Sep 29, 2009 at 4:20 PM, Brett Wilson bre...@chromium.org wrote: On Tue, Sep 29, 2009 at 4:15 PM, Jeremy Orlow jor...@chromium.org wrote: I'm guessing different people/companies will have different needs for a kiosk mode. Maybe all of these should be separate flags rather than one kiosk flag? We could then offer recommendations in a Chromium for kiosks Wiki page? I think the reasoning for allowing this feature is that some minority would find it helpful and it wouldn't hurt much. I'm concerned that it is getting much too complicated. I think we shouldn't do it if it is going to be this complicated. Would multiple command line flags rather than one really complicate the design? Mohamed's original patch was just a bunch of if statements keying off of one flag. Seems like the same amount of work to have each if statement key off of a different one. Or am I missing something? If nothing else, it grows the configuration space. Supporting a kiosk mode seems like a good idea. Supporting 2^N different flavors of kiosk mode sounds dicier. -- Jacob --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
I think I'm right to say that a lot of the knobs stated by Mohamed can be achieved with content script. Everything that can be done with javascript for this particular use case should be done as javascript. For example, destroying the window.print prototype. I think you try to block to many things. For example, quitting the browser is probably a no-op, the script managing the browser life-time it should just restart it. It would be required anyway in case of a browser crash. Tabs aren't a big deal either. Can you can hook into tabs with extensions but I don't know if you can block their creation though. If this could be done with almost only pure javascript (in addition to --fullscreen or --app), that would be awesome, especially unit test wise. M-A On Tue, Sep 29, 2009 at 7:45 PM, Jacob Mandelson ja...@mandelson.org wrote: On Tue, Sep 29, 2009 at 04:37:46PM -0700, Jeremy Orlow wrote: On Tue, Sep 29, 2009 at 4:20 PM, Brett Wilson bre...@chromium.org wrote: On Tue, Sep 29, 2009 at 4:15 PM, Jeremy Orlow jor...@chromium.org wrote: I'm guessing different people/companies will have different needs for a kiosk mode. Maybe all of these should be separate flags rather than one kiosk flag? We could then offer recommendations in a Chromium for kiosks Wiki page? I think the reasoning for allowing this feature is that some minority would find it helpful and it wouldn't hurt much. I'm concerned that it is getting much too complicated. I think we shouldn't do it if it is going to be this complicated. Would multiple command line flags rather than one really complicate the design? Mohamed's original patch was just a bunch of if statements keying off of one flag. Seems like the same amount of work to have each if statement key off of a different one. Or am I missing something? If nothing else, it grows the configuration space. Supporting a kiosk mode seems like a good idea. Supporting 2^N different flavors of kiosk mode sounds dicier. -- Jacob --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
How about in kiosk mode, we only hide the status bubble, control the command dispatchers, and we leave the context menu as it is. That will solve most of the issues and not complicate things. Windows defined it pretty simple, http://support.microsoft.com/kb/154780, they can open new windows, tabs, close, etc. I believe it is a correct way to follow, its not illegal or anything to follow something that is good and working. And it will make the patch easy and simple. -Mohamed On Tue, Sep 29, 2009 at 8:27 PM, Marc-Antoine Ruel mar...@chromium.orgwrote: I think I'm right to say that a lot of the knobs stated by Mohamed can be achieved with content script. Everything that can be done with javascript for this particular use case should be done as javascript. For example, destroying the window.print prototype. I think you try to block to many things. For example, quitting the browser is probably a no-op, the script managing the browser life-time it should just restart it. It would be required anyway in case of a browser crash. Tabs aren't a big deal either. Can you can hook into tabs with extensions but I don't know if you can block their creation though. If this could be done with almost only pure javascript (in addition to --fullscreen or --app), that would be awesome, especially unit test wise. M-A On Tue, Sep 29, 2009 at 7:45 PM, Jacob Mandelson ja...@mandelson.org wrote: On Tue, Sep 29, 2009 at 04:37:46PM -0700, Jeremy Orlow wrote: On Tue, Sep 29, 2009 at 4:20 PM, Brett Wilson bre...@chromium.org wrote: On Tue, Sep 29, 2009 at 4:15 PM, Jeremy Orlow jor...@chromium.org wrote: I'm guessing different people/companies will have different needs for a kiosk mode. Maybe all of these should be separate flags rather than one kiosk flag? We could then offer recommendations in a Chromium for kiosks Wiki page? I think the reasoning for allowing this feature is that some minority would find it helpful and it wouldn't hurt much. I'm concerned that it is getting much too complicated. I think we shouldn't do it if it is going to be this complicated. Would multiple command line flags rather than one really complicate the design? Mohamed's original patch was just a bunch of if statements keying off of one flag. Seems like the same amount of work to have each if statement key off of a different one. Or am I missing something? If nothing else, it grows the configuration space. Supporting a kiosk mode seems like a good idea. Supporting 2^N different flavors of kiosk mode sounds dicier. -- Jacob --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.org wrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
You can create a content script that will disable the shortcut keys of the browser and the right clicks, on all of the pages.About browsing to other pages (and so, downloading), you can apply a rule within a content script to always navigate to the home page of what you need, when going to any other URL. That would solve most of the issues you have in that list. ☆PhistucK On Fri, Sep 25, 2009 at 15:30, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.orgwrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
What are the major issues?Full screen with no escape hatch and no status bubble? Chrome developers already said the are willing to take care of those\accept patches for those. The rest are taken care of with disabling keyboard shortcuts, or am I wrong? ☆PhistucK On Fri, Sep 25, 2009 at 15:44, Mohamed Mansour m...@chromium.org wrote: The minor issues, yes, the major issues, no. -Mohamed On Fri, Sep 25, 2009 at 8:40 AM, PhistucK phist...@gmail.com wrote: You can create a content script that will disable the shortcut keys of the browser and the right clicks, on all of the pages.About browsing to other pages (and so, downloading), you can apply a rule within a content script to always navigate to the home page of what you need, when going to any other URL. That would solve most of the issues you have in that list. ☆PhistucK On Fri, Sep 25, 2009 at 15:30, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.orgwrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.orgwrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly
[chromium-dev] Re: Kiosk Mode for Chrome
Something as simple as this:http://codereview.chromium.org/244003 http://codereview.chromium.org/244003Not necessarily clean, but this thread is whether we would want to implement Kiosk mode in Chromium. That will help many companies to use Chromium as their solution for hosting their web products. -Mohamed On Fri, Sep 25, 2009 at 8:47 AM, PhistucK phist...@gmail.com wrote: What are the major issues?Full screen with no escape hatch and no status bubble? Chrome developers already said the are willing to take care of those\accept patches for those. The rest are taken care of with disabling keyboard shortcuts, or am I wrong? ☆PhistucK On Fri, Sep 25, 2009 at 15:44, Mohamed Mansour m...@chromium.org wrote: The minor issues, yes, the major issues, no. -Mohamed On Fri, Sep 25, 2009 at 8:40 AM, PhistucK phist...@gmail.com wrote: You can create a content script that will disable the shortcut keys of the browser and the right clicks, on all of the pages.About browsing to other pages (and so, downloading), you can apply a rule within a content script to always navigate to the home page of what you need, when going to any other URL. That would solve most of the issues you have in that list. ☆PhistucK On Fri, Sep 25, 2009 at 15:30, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.orgwrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.orgwrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.org wrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in
[chromium-dev] Re: Kiosk Mode for Chrome
Sorry for not being clear. What I meant was that you could create your own kiosk shell and embed Chrome Frame as ActiveX control to render the pages you want in it. That way you could customize different features up to your own satisfaction. On Fri, Sep 25, 2009 at 5:30 AM, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.orgwrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
Well, Mohamed's patch is *way* simpler and portable. On Fri, Sep 25, 2009 at 12:40 PM, Amit Joshi a...@chromium.org wrote: Sorry for not being clear. What I meant was that you could create your own kiosk shell and embed Chrome Frame as ActiveX control to render the pages you want in it. That way you could customize different features up to your own satisfaction. On Fri, Sep 25, 2009 at 5:30 AM, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar - Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.org wrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.org wrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.org wrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Fri, Sep 25, 2009 at 5:30 AM, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) wait, did you do '... -k cf:http://www.google.com'? (Or does the Google home page use Chrome Frame?) (Not that I'm saying this is the right route. It sounds like a command line flag for Chrome might be the best way to go!) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.orgwrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
Hi Jeremy, ChromeFrame doesn't seem to work if you pass the URL in command line for Internet Explorer. A simple example is visiting this page directly (assuming you installed ChromeFrame) 1. Open Internet Explorer 2. Visit this http://haptisense.com/ 3. You will see the correct After Browser which is Chrome and Original Browser which is IE. Now do this: 1. cd C:\Program Files\Internet Explorer 2. Type: iexplorer.exe http://haptisense.com 3. You will see the correct Original Browser but the After Browser is still IE (you can notice the Chrome renderer isn't replaced because there is IE right click and rendering is obviously IE) Same thing happens to iexplorer.exe -k http://haptisense.com The patch I submitted, does what I wanted to do for demo purposes, I contribute to Chrome because I love everything about this browser, and seeing the usage of IE in my day job is quite annoying (since our GIS web apps are plotting horribly slow in comparison to Chrome if given a lot of data). I could submit a cleaner patch (which does it right) that introduces Kiosk mode for Chrome. Are there any *objections*? -Mohamed On Fri, Sep 25, 2009 at 12:51 PM, Jeremy Orlow jor...@chromium.org wrote: On Fri, Sep 25, 2009 at 5:30 AM, Mohamed Mansour m...@chromium.org wrote: I tried ChromeFrame it is very good, but it doesn't work if the Kiosk Mode flag is set. If the Kiosk mode is set ( iexplorer.exe -k http://www.google.com ) it renders it as IE Renderer. It renders it fine in a Chrome Frame if its not in Kiosk mode. That must be a bug :) wait, did you do '... -k cf:http://www.google.com'? (Or does the Google home page use Chrome Frame?) (Not that I'm saying this is the right route. It sounds like a command line flag for Chrome might be the best way to go!) For IE, kiosk mode has a context menu, but people usually apply the registry tweak to remove context menu from IE if they need to. For Chromium, it would be nice if stuff like this would be an extension, an extension should allow us to show/hide various parts of the UI. In the meantime, I quickly compiled a custom Chromium so that my CEO and VP could see the benefits of using Chrome instead of IE on some of our web products. Stuff that would be cool and would be very lightweight to include for kiosk mode would be: - No Status Bar- Full Screen (with no exit, only alt+f4 should work) - No Context Menus (should be an option) - Disable downloading of files. - No tabs - No opening files - many more I would rather that be an extension (but there are currently no way to actually block users to remove extensions, maybe blocking users entering a url would suffice) but not possible currently. -Mohamed On Fri, Sep 25, 2009 at 1:52 AM, Amit Joshi a...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.orgwrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version,
[chromium-dev] Re: Kiosk Mode for Chrome
On Fri, Sep 25, 2009 at 10:43 AM, Mohamed Mansour m...@chromium.org wrote: I could submit a cleaner patch (which does it right) that introduces Kiosk mode for Chrome. Are there any objections? None from me. :) Adam --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
No objections. I think it's a good idea, you're not the only one who wants this, and it seems like it can be done very cleanly. On Fri, Sep 25, 2009 at 10:47 AM, Adam Barth aba...@chromium.org wrote: On Fri, Sep 25, 2009 at 10:43 AM, Mohamed Mansour m...@chromium.org wrote: I could submit a cleaner patch (which does it right) that introduces Kiosk mode for Chrome. Are there any objections? None from me. :) Adam --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
Have you considered using Google Chrome Frame instead? That would let you keep all your existing IE7 integration points but have the rendering speed up by the factor of 10 that you cited. Adam On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.org wrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
IIRC, someone asked this a couple months ago. I believe the answer was that http://code.google.com/p/chromiumembedded/ might be of interest. I could see patches being welcome as long as they were fairly clean. I know that's not an official answer, but you're probably not going to get a yes from anyone unless they can see the impact it'd have. J On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.org wrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.org wrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.org wrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Thu, Sep 24, 2009 at 10:32 PM, Adam Barth aba...@chromium.org wrote: On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.org wrote: Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? Darin is right that this is easy to do and support. We could also turn off other features that don't make sense for kiosks, like downloading files. But doing this stuff you added is when the support costs start getting nontrivial and why these features are often a risky road to travel. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.org wrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
Actually, ChromeFrame is not yet an option on Mac or Linux.-Darin On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.org wrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Kiosk Mode for Chrome
On Thu, Sep 24, 2009 at 10:47 PM, Darin Fisher da...@chromium.org wrote: Chrome Frame is a good option, but you'd still need a way to turn off some features. For example, a kiosk probably doesn't want to have a context menu. Chrome Frame can/will offer control over the context menu. This is exactly the kind of customization Chrome Frame can offer. Too bad we don't have Linux, Mac versions yet, but we are open source now so patches welcome :) -Darin On Thu, Sep 24, 2009 at 10:24 PM, Amit Joshi a...@chromium.org wrote: I think you should really consider embedding chrome frame ActiveX in your own simple shell. That will not only enable the application to be started with desired real estate and get rid of status bubble but allow you to customize it further if needed. On Thu, Sep 24, 2009 at 10:07 PM, Darin Fisher da...@chromium.orgwrote: On Thu, Sep 24, 2009 at 11:37 AM, Mohamed Mansour m...@chromium.orgwrote: At work today, I talked to the CEO of my company to ship Chrome browser with all our Kiosk's and recommended Chrome to be our default browser for our web products. I bench marked our current web applications with Chrome (ToT) vs IE 7, and our applications run at average 10 times faster. (For windows, Mac speed differed) There are some stuff that he didn't like: 1. Status Bubble: for a cashiering application, it keeps popping up every second since buttons are all over the place. It was distracting him from the main product. 2. Full screen mode always = Kiosk Mode. He wants the web app to stay full screen, in IE, there is kiosk mode command line switch. In FF there is a plugin. 3. JavaScript errors kept appearing intermittently (on the Mac), would work on initial deploy but require a Clear browsing data on subsequent runs. Works great on windows (chrome). I guess we would be using linux/windows for kiosk anyhow. Will there be plans for us to introduce Kiosk Mode in Chrome? It seems the current audience is just targeted towards home users and there is no way to use Google Chrome for other usages. Sure we could compile our own Chromium version, but many people (Chrome forums and elsewhere) would like to use Chrome commercially. In the meantime, I am going to compile a version with no status bar, but I believe it would be nice to include it in future versions. Maybe we could allow extensions to control (hide/show) different areas in chrome. Maybe I'm in the minority, but it doesn't sound that unreasonable to support command line options for disabling the status bubble and starting in full screen mode. We could lump these together into a --kiosk-mode command line flag. This seems like something that could be done in a fairly lightweight manner. Maybe others object? -Darin --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
