Last modified: 2013-08-15 10:06:35 UTC
visual editor easily doubles mouse clicks and key presses. this can be seen, amongst others, on section editing, saving, adding a reference. to avoid bug reports in the line of "please remove one mouse click while creating a reference" create a (visual) design guideline mandatory to follow for all developers to minimize mouse clicks and key presses, and maximise screen estate available for editing/viewing the article.
Which exact problem do you see with the current situation, that made you file this bug report?
for bug48429, section editing, i tried VE at https://en.wikipedia.org/wiki/Jos%C3%A9_Mourinho. to repeat the clicks and key presses here: * 1 click and 15 secs to edit * 1 click to make go a away a note (see attachment) * 1 click to edit summary * 1 click and 20 secs to review changes * 1 click to return to save form * 1 click and 40 secs to save * 5* pg down to go to the section just edited while text editor sections can be edited with: * 1 click and 2 secs to open * 1 click and 2 secs to preview * 1 pg-down to find the save button (could be avoided by re-placing the button) * 1 click and 10 secs to save old is ideally 3 clicks, new is 6 clicks + 5 key presses. but, there are other cases as well. to add a category with hotcat is one click and a key press to confirm. It auto-corrects even the spelling to upper case. VE takes 8 clicks, a refresh, and scrolling down, if i counted correctly.
Of course, this is already our intention. There is nothing to "create". Bugzilla is not really the right place to suggest user experience improvements like this - though walk-through data like you've given is hugely valuable, and if you have more I would love for you to share it.
james, let me reopen this one please. there is a big difference between "it is our intention" (whoever "our" is) and a crystal clear guideline having as primary target: * minimize clicks and key presses * response time <3 sec this would make it so much easier for new developers as well. and so much easier for testers to point out that something is against the goal. as i tried to point out above with examples, people were and still are allowed to increase key presses and mouse-clicks considerable compared to the existing solution. i tried to look for design documents or mail references on some tech list to find a justification for this, but could not find one. you as a software developer surely know that nothing is more expensive than fixing a design bug. and nothing is more expensive than finding a bug late. just to take an arbitrary url to support this: http://blog.bootstraptoday.com/2011/12/25/early-detection-of-bugs-can-save-up-to-22-billion-yearly/ so, please do not play the "a good thing but not the right place" card. which then ends up nowhere. you can close the ticket if you either create this guideline, or successfully have a (public verifyable) decision in whatever place you consider right for a decision like this.
Again: This won't be handled in Bugzilla, however pointing to a better place where to discuss would be very good. Playing the "I know it's the wrong place but still I want to discuss it here" card isn't much better either though. :) Please don't reopen as a sign of disagreement. Thanks.
