Re: [chromium-dev] [WebGL] Recommending --no-sandbox
We actually rarely ask users to turn off the sandbox and after we confirm that they can run it with the flag, we tell them do remove it immediately due to security vulnerabilities. The only problem is that after this point, it's hard for users to figure out what's preventing Google Chrome to run properly. We need to find an easier way or some sort of utility to do this. I agree that we need to make it obvious to the user that they shouldn't be running without sandbox but we need to give them a better way to figure out what's wrong so that they can continue to use it. On Fri, Dec 11, 2009 at 11:48 AM, John Abd-El-Malek wrote: > (adding Alice) > > Alice: do you have a rough estimate for how often we ask users to turn off > the sandbox when debugging problems? > > Thanks > > > On Fri, Dec 11, 2009 at 11:33 AM, John Abd-El-Malek wrote: > >> >> >> On Thu, Dec 10, 2009 at 11:34 PM, Darin Fisher wrote: >> >>> I don't think we should take away --no-sandbox in official builds. It's >>> a valuable debugging tool in case an end-user is experiencing a startup >>> crash or other wackiness. >> >> >> I understand the argument, but do we really end up using this for >> end-users in debugging problems? Given how many Chrome users we have, my >> impression is we've fixed any issues with the sandbox long ago. >> >> I don't feel that strongly about disabling --no-sandbox, but I'd like to >> be more convinced of the arguments against it :) >> > >> >>> I think we should just add a modal dialog at startup that you must >>> dismiss each time you launch Chrome until you remove the --no-sandbox >>> option. That should be annoying enough to cause people to remove it once >>> they can. We don't need to expend energy on anything fancier IMO. >>> >>> -Darin >>> >>> >>> On Thu, Dec 10, 2009 at 11:02 PM, John Abd-El-Malek >>> wrote: >>> >>>> >>>> >>>> On Thu, Dec 10, 2009 at 10:57 PM, Jeremy Orlow wrote: >>>> >>>>> On Thu, Dec 10, 2009 at 10:25 PM, Peter Kasting >>>>> wrote: >>>>> >>>>>> On Thu, Dec 10, 2009 at 9:38 PM, John Abd-El-Malek >>>>>> wrote: >>>>>> >>>>>>> We disable --single-process and --in-process-plugins on release >>>>>>> Google Chrome builds to avoid the support headache that it causes. I >>>>>>> think >>>>>>> we should do the same for --no-sandbox. >>>>>> >>>>>> >>>>>> There are legit reasons we have asked users to try temporarily >>>>>> disabling the sandbox, more frequently than for those other flags. I'd >>>>>> prefer to just make the UI turn ugly a la Jeremy's bug. >>>>>> >>>>> >>>>> It might even make sense to re-enable --single-process and use the same >>>>> UI technique to discourage it. >>>>> >>>> >>>> --single-process is buggy and not well tested, and can cause deadlocks >>>> in some scenarios. >>>> >>>> I think only developers should run without the sandbox, as those are the >>>> ones who'd be able to understand the risks in doing so, and are the only >>>> ones who need to test out features like webgl that aren't ready yet. So I >>>> still think we should disable --no-sandbox in shipping Google Chrome >>>> builds, >>>> and if someone needs it, they can use Chromium builds. >>>> >>> >>> >> > -- Alice Lin | Google, Inc. | Senior Strategist, Consumer Operations | 650.253.6827 | a...@google.com This email and the information it contains are confidential and may be privileged. If you have received this email in error please notify me immediately. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and, therefore, Google does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. If you suspect the message may have been intercepted or amended please contact me. -- 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: Question about UI and "classic views"
Preliminary feedback shows that people are having a hard time fully embracing the new tab page. While they love the fact that now they can move, pin, hide thumbnails, other more vocal users are really missing the customized search boxes. We'll continue to monitor. On Wed, Sep 23, 2009 at 10:43 PM, Brian Rakowski wrote: > We did test it in the lab, though we focused on new users who seemed to > like it. We also looked at stats which indicated that the Most visited and > Recently closed items were the only things that were actually used. The few > people who used Recent bookmarks and Searches have been vocal, but we know > there weren't many of them. > We are also listening to user support (Alice tells us that feedback is > mixed between love it an hate it). A more in-depth user support report is > coming soon. > > We expect to continue trying to improve the NTP, so feedback is definitely > welcome. > > -Brian > On Wed, Sep 23, 2009 at 9:38 PM, Mike Belshe wrote: > >> On Wed, Sep 23, 2009 at 9:04 PM, Ben Goodger (Google) >> wrote: >> >>> One day, we may offer further customization of this page. This may >>> include the ability to show more items. I think this is preferable to >>> a "classic view" option, which sets a bad precedent - that every time >>> we make a UI change we'll carry the burden of supporting the old way >>> too forever. It adds to the testing matrix and raises the opportunity >>> cost of making ambitious UI changes. >>> >> >> I think you've got the precedent problem backwards. Look at it from the >> other side. The precedent that we set is that users should not expect any >> say or control about the UI. And if you, the user, don't like it, well, go >> back to IE, because we, Chrome, think our support burden is more important >> than your browser preferences. Is that the precedent we want to set? >> >> I'm not really fighting for the old UI, but I am fighting that we are >> aware of the negative consequences of change and that we better help users >> through transitions. If other users are saying the same thing, we might >> want to be a bit more sympathetic. >> >> Did we do usability studies of the NTP with existing users? Did they >> universally like the new layout better? Should we have had better upgrade >> UI so that users knew this was happening? >> >> Mike >> >> >> >> >>> >>> -Ben >>> >>> On Wed, Sep 23, 2009 at 8:59 PM, Mike Belshe wrote: >>> > I just got a fairly angry email from my sister about the new tab page >>> UI. >>> > She writes: >>> >> >>> >> "What’s up with the Chrome Tab page change? I thought I screwed up my >>> >> page at home, but now my page at work has changed too. >>> > >>> > I don’t like it. >>> > >>> > Why do I have to have my tabs arranged 4x2 ? I liked 3x3. >>> > >>> > What happened to the delete tabs? >>> > >>> > Do we get no say in what our page looks like? Google just gets to >>> make the >>> > change without so much as a notice, “Your page has changed for the >>> worse”. >>> > >>> > Sorry to dump on you but, it sure is nice thinking that I can gripe >>> to >>> > someone at a giant company like Google and there actually might be >>> someone >>> > listening." >>> > >>> > This is probably a good point; why didn't we offer a "classic view" >>> option >>> > to users? It is not like the current new-tab-page is all that >>> radically >>> > different. I'm sure we were aware that some users would feel this way? >>> But >>> > we think we know better than they do what this page should look like? >>> > >>> > BTW - I liked 3x3 better than 4x2 better too. >>> > >>> > Mike >>> > >>> > > >>> > >>> >> >> >> >> > > > > -- Alice Lin | Google, Inc. | Senior Strategist, Consumer Operations | 650.253.6827 | a...@google.com This email and the information it contains are confidential and may be privileged. If you have received this email in error please notify me immediately. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and, therefore, Google does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. If you suspect the message may have been intercepted or amended please contact me. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
