Live data from Hacker News

Buttons with built-in loading indicators

lab.hakim.se

21–30 of 64 posts

Re: Buttons with built-in loading indicators

#21

This is really cool! The only thing that makes it a little ugly for me is that when I click on it, my browser puts an ugly grey box around the text like I'm selecting it. Could this be solved by immediately changing the focus of the input?

please don't mess with focus that way, it ruins accessibility.

Re: Buttons with built-in loading indicators

#22
post #21

This is really cool! The only thing that makes it a little ugly for me is that when I click on it, my browser puts an ugly grey box around the text like I'm selecting it. Could this be solved by immediately changing the focus of the input?

please don't mess with focus that way, it ruins accessibility.

These buttons become unclickable once clicked upon. There is no additional loss of accessibility if you remove focus at this point, on the contrary.

Re: Buttons with built-in loading indicators

#23
post #6

It's not known very well, but Bootstrap has similar functionality, albeit not as pretty: http://twitter.github.io/bootstrap/javascript.html#buttons

As long as te app won't "break" by the user navigating away, anything that avoids the "loading" modal is a great UX improvement. Ajax errors can also be sent to the button with "error" icon, BTW.

Re: Buttons with built-in loading indicators

#24
post #22
post #21

Earlier quoted context omitted.

please don't mess with focus that way, it ruins accessibility.

These buttons become unclickable once clicked upon. There is no additional loss of accessibility if you remove focus at this point, on the contrary.

the unclickability is also an accessibility issue imo. I know which problem it solves, but creates another when the site becomes unresponsive due to connection loss etc.

Re: Buttons with built-in loading indicators

#26
post #24
post #22

Earlier quoted context omitted.

These buttons become unclickable once clicked upon. There is no additional loss of accessibility if you remove focus at this point, on the contrary.

the unclickability is also an accessibility issue imo. I know which problem it solves, but creates another when the site becomes unresponsive due to connection loss etc.

I agree with you on that. The primary usage mode for these buttons are probably AJAX forms, and those can be very frustrating for lots of reasons. I think it's great to have some kind of visual feedback that you're action is being performed, but at the same time transmissions errors should not result in a stuck app. That's why I think the UI practice suggested by these buttons is likely to result in user frustration, but still there is no additional usability loss when removing the focus from an already disabled button.

Re: Buttons with built-in loading indicators

#28
post #24
post #22

Earlier quoted context omitted.

These buttons become unclickable once clicked upon. There is no additional loss of accessibility if you remove focus at this point, on the contrary.

the unclickability is also an accessibility issue imo. I know which problem it solves, but creates another when the site becomes unresponsive due to connection loss etc.

Genuinely interested: how would it be more usable if the buttons remained clickable after they'd been clicked? If you lost your connection, wouldn't you expect some kind of error? In that case how would it be more usable to be able to click the button again?
Post reply on HN