> There are two purposes: > > * The initial purpose was to abort scripts that are looping as they > are primary considered malicious. > > * The second pupose is to continue scripts because your system is too > slow for the javascript application. > >For initial case, the idea is to guide the user to Stop the script > ... so using green makes sense for Stop. > > Now we have second valid use case ... its hard to decide.
I see. I absolutely agree that it should be obvious for the user that faces a run-away script that she should click Stop. Leaving the Stop button the default one, which it is now, can help. For me, stop is never supposed to be green, whether it is "bad" stop I'd like to avoid or a "good" stop I want to perform. Green means "go" in this context, and stop is just not go. Show me where is stop, and I'll then choose whether I want it or not, even if it's red. The best way to properly resolve this is to conduct a tiny usability study. Testing with five non-programmers would be enough, as Jakob Nielsen has shown, if you don't make some beginner's mistakes in the process. Even showing them just colored paper prototypes is usually much better than no user testing at all. If we can't think of some usable unambiguous icons for Stop and Continue, we are better off without either one. After all, the icons are supposed to make the text more obvious at a glance, not the opposite. And please don't forget about information loss issue on slower machines. I'm not sure how likely it is to occur with real web applications, but if it does, it will be really frustrating for the users. Really. -- Unresponsive script dialog usability problems https://bugs.launchpad.net/bugs/127960 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
