UI: solutions that satisfy all usercases
- ferongr
- Posts: 537
- Joined: February 16th, 2011, 9:51 am
UI: solutions that satisfy all usercases
I feel sad when reading comments about UI changes (see bug 695482). Why can't Mozilla devs rationally decide on the best solution that will please all usercases, and allow for personalization, instead of putting their egos first?
Last edited by ferongr on November 30th, 2011, 6:52 am, edited 2 times in total.
What Falken giveth, the tōge taketh away.
- mikedl
- Posts: 1236
- Joined: October 14th, 2010, 4:47 pm
- Location: Florida, USA
Re: The Official Win32 20111130 builds are not yet out
Well, ferongr, we still have .css code and a bunch of people that can make Fx do what you want.
"It may be that there are true demonstrations; but this is not certain. Thus, this proves nothing else but that it is not certain that all is uncertain, to the glory of skepticism." Pascal's Pensées
- LoudNoise
- New Member
- Posts: 39900
- Joined: October 18th, 2007, 1:45 pm
- Location: Next door to the west
Re: The Official Win32 20111130 builds are not yet out
Angst isn't on topic folks. Start a new thread please.
Post wrangler
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
- Omega X
- Posts: 8225
- Joined: October 18th, 2007, 2:38 pm
- Location: A Parallel Dimension...
Re: The Official Win32 20111130 builds are not yet out
Heh, they locked it off. I guess I'll find out sooner or later.
- Binary Alchemist
- Posts: 36
- Joined: May 21st, 2010, 3:30 pm
- Location: Caracas, Venezuela
Re: The Official Win32 20111130 builds are not yet out
Dunno... maybe ferongr mistyped the bug number? I cannot locate even a description for bug #694582, but bug #695482 is pinklisted above and matches his comment.
BTW, "... decide on the best solution that will please all usercases." Sorry, that only exists for very trivial problems. Not the case.
Edit: URL styling.
BTW, "... decide on the best solution that will please all usercases." Sorry, that only exists for very trivial problems. Not the case.
Edit: URL styling.
“Do you understand what’s going on?”
“Not at all,” he shouted back. “I can almost prove this can’t be happening.”
Firefox Release Engineering Carl Sagan, Contact
“Not at all,” he shouted back. “I can almost prove this can’t be happening.”
- LoudNoise
- New Member
- Posts: 39900
- Joined: October 18th, 2007, 1:45 pm
- Location: Next door to the west
Re: Ui: best solution that will please all usercases.
Split off the nightly thread.
Post wrangler
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
"Choose between the Food Select Feature or other Functions. If no food or function is chosen, Toast is the default."
- Omega X
- Posts: 8225
- Joined: October 18th, 2007, 2:38 pm
- Location: A Parallel Dimension...
Re: Ui: best solution that will please all usercases.
Ahh, thanks Alchemist.
AFAIK, this is a parity change more than anything.
- Two out of the other four major browsers open the search in a tab and immediately focuses it. (Chrome/IE)
- The other two immediately does the search in the same tab. (Opera/Safari)
AFAIK, this is a parity change more than anything.
- Two out of the other four major browsers open the search in a tab and immediately focuses it. (Chrome/IE)
- The other two immediately does the search in the same tab. (Opera/Safari)
- ferongr
- Posts: 537
- Joined: February 16th, 2011, 9:51 am
Re: Ui: best solution that will please all usercases.
(Never make posts when sleepy)
"OOB" parity, I have no problem with, but when someone changes something that has been working the same way for years, he/she should at least provide an about:config option that allows the user to return to the previous way something worked. No, options are not "extension territory, that's just a cheap excuse to prevent people from easily changing to the old behavior, making the original change unpopular resulting in a backout. The same happened with "Switch to Tab".
"OOB" parity, I have no problem with, but when someone changes something that has been working the same way for years, he/she should at least provide an about:config option that allows the user to return to the previous way something worked. No, options are not "extension territory, that's just a cheap excuse to prevent people from easily changing to the old behavior, making the original change unpopular resulting in a backout. The same happened with "Switch to Tab".
What Falken giveth, the tōge taketh away.
-
- Posts: 144
- Joined: April 26th, 2009, 1:36 am
Re: Ui: best solution that will please all usercases.
I'd be happy with a config option, which makes the most sense to me. I never expected one in UI.
Trying to achieve the same thing with an extension requires 1) someone to write it, 2) someone to maintain it, and 3) the user to seek it out. And does Mozilla really want to rely on the often creaky and conflicted add-ons system to restore previous behaviors and other simple things? The UX people probably don't give much thought to it, but other folks might not welcome even more grist for the compatibility mill.
And finally, "parity" is a two-edged sword. I use Fx because I like the way it acts, not because it acts like Chrome, Safari, or what have you. Making it a pale imitation of the others only makes it more likely that I'll use them instead. There are deeper failings in Fx that are tolerable only because other traits make up for them. Remove enough of those traits, and it will become a case of "why bother?"
Trying to achieve the same thing with an extension requires 1) someone to write it, 2) someone to maintain it, and 3) the user to seek it out. And does Mozilla really want to rely on the often creaky and conflicted add-ons system to restore previous behaviors and other simple things? The UX people probably don't give much thought to it, but other folks might not welcome even more grist for the compatibility mill.
And finally, "parity" is a two-edged sword. I use Fx because I like the way it acts, not because it acts like Chrome, Safari, or what have you. Making it a pale imitation of the others only makes it more likely that I'll use them instead. There are deeper failings in Fx that are tolerable only because other traits make up for them. Remove enough of those traits, and it will become a case of "why bother?"
-
- Posts: 235
- Joined: March 13th, 2011, 1:15 pm
Re: Ui: best solution that will please all usercases.
Omega X wrote:Ahh, thanks Alchemist.
AFAIK, this is a parity change more than anything.
- Two out of the other four major browsers open the search in a tab and immediately focuses it. (Chrome/IE)
- The other two immediately does the search in the same tab. (Opera/Safari)
FWIW in Opera opening in a the current tab can be disabled by turning off "reuse current tab" in the settings. Also, ctrl+clicking the menu item opens it in a background tab and shift+clicking opens it in a new foreground tab. So there's an option + hotkeys to do different things with the default. It seems like Firefox could do something similar.
- sabret00the
- Posts: 1396
- Joined: June 29th, 2004, 8:24 am
- Location: London (UK)
- Contact:
Re: UX: solutions that satisfy all usercases
FWIW, if I open a search in a new tab, it's normally to be checked after I've finished with the current tab, not midway through reading whatever I'm reading.
-
- Posts: 1021
- Joined: November 7th, 2002, 11:15 pm
Re: UX: solutions that satisfy all usercases
sabret00the wrote:FWIW, if I open a search in a new tab, it's normally to be checked after I've finished with the current tab, not midway through reading whatever I'm reading.
I use it both ways, but it makes complete sense to me that the "open in background" preference would apply. I'm fine with them changing the default behavior, what I'm not fine with is them removing control over the behavior. What makes Firefox great is that control.
-
- Posts: 75
- Joined: October 28th, 2008, 6:35 am
Re: UI: solutions that satisfy all usercases
While I understand that nothing will work for everyone I was mainly frustrated because it seems to me that they changed how everyone was used to working with the search option and negating the Background Tabs setting because a couple people thought that was how it was supposed to work. The fact that they didn't do any user tests just adds to it. Comment 15 for me just takes the cake in that the answer to a change was to use an extension to change it back. Why not use an extension to make the change in the first place? I mean that why things like Tab Mix Plus still exist.
-
- Posts: 377
- Joined: January 31st, 2010, 11:15 am
Re: UI: solutions that satisfy all usercases
UI Suggestion: Http basic authentication user/pass input messagebox shouldn't block the whole Browser Interaction (fixed window)
- patrickjdempsey
- Posts: 23686
- Joined: October 23rd, 2008, 11:43 am
- Location: Asheville NC
- Contact:
Re: UI: solutions that satisfy all usercases
Gah, another search-related change that is for people who only do one search at a time. If I'm researching a topic I may open 5 or 6 related search queries as I go and switch back and forth... but I don't want to have to manually go back to my original article after hitting search. If people can't figure out that the search opened in a new tab, then Mozilla needs to do what they should have done years ago... highlight unread tabs.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/