I filed this super minor issue in the browserid issue tracker and it was closed with 'as designed'. No feedback as to why it was designed this way, but it sure seems silly to me to hide the 'remove' button under an 'edit' button.
I can understand this on a UI like an iPhone, but on a web page?
Wow, that's just silly. I agree - "Delete" is simply not a subset of "Edit"ing an option in a configuration. It may be a subset of editing the entire configuration, but having a two-step process that makes a non-connected action into a child action is mind boggling. People need to learn their CRUD/BREAD better.
tl;dr: Super minor, but the case of buttons is actually important UX too.
I'm worried about BrowserID UX because we are implementing it on our site as an additional login system along with Facebook Connect. I'd love to see BrowserID become successful since we need an alternative to Facebook and OpenID is a train wreck. But, I worry that with bad UX, it will remain just an unused interesting idea.
Yeah, but I'm probably just used to it and since I was referring to BREAD, it kind of made sense. I guess it's one of those age old questions like "do we say 'your' or 'my'?".
Here is another semi-close example. Not about hovering, but how about needless hiding of important user experience?
https://github.com/mozilla/browserid/issues/797
I filed this super minor issue in the browserid issue tracker and it was closed with 'as designed'. No feedback as to why it was designed this way, but it sure seems silly to me to hide the 'remove' button under an 'edit' button.
I can understand this on a UI like an iPhone, but on a web page?
Oh well.