My favorite part was how s-l-o-w-l-y the "How Can We Help?" dialog sank when I clicked Send to Bottom. I also appreciate how it would reappear and block the interface. But kind of disappointed it didn't instantly reappear if you moused over it. Or that it didn't randomly bounce for attention in my peripheral vision. And to the person out there thinking of making a front end framework based on this, just don't do it m…
I had this happen today, in the wild, after visiting a HN linked Wired article. A few seconds on the page, a banner appears, blocking about a quarter of the page. Close it, start reading the article. 30 seconds later, the original banner reappears, again blocking a quarter of the page, and I close it again. I continue reading, think I hit a "click to read more button", another click. Keep reading, maybe two thirds of…
User Inyerface – A worst-practice UI experiment
251–260 of 266 posts
Re: User Inyerface – A worst-practice UI experiment
#252Earlier quoted context omitted.
Oh I definitely recognise this, it's using Microsoft's Bot Framework ( https://dev.botframework.com/ ). I had to make a chatbot for a hospital during my end of studies internship. I still don't get why people want chatbots as they're terrible UI, so frustrating to use even when they're made properly.
People don't want chatbots - businesses want(ed) them because they offer(ed) the promise of much cheaper support. Of course that's predicated on them working at all , which in practice they don't, obviously. Think that message has filtered through enough now that the hype surge that was in full swing a couple of years ago seems to have petered out again.
I wonder if I'm currently missing some slice of web life by not using any ‘support’ chat interfaces ever.
Re: User Inyerface – A worst-practice UI experiment
#253Earlier quoted context omitted.
Some time ago I tried registering an account on a site where the password policy was that you couldn't use special characters and that it would discard any characters you entered after the first 15 ones. But you know what the worst part was? They never bothered informing you about these limitations. The site just returned a generic error. Not supporting special characters I can kinda understand but silently discardin…
I once registered a password using a special character, but I could not get in. It turned out that they url encoded it, if I used %21 instead of "!" I could get into the site.
I saw a screenshot of an error dialogue on Reddit once (so possibly fake, but still hilarious) that said something like:
"You cannot use that password, because it's already in use by user Kegstand360"
Re: User Inyerface – A worst-practice UI experiment
#254I LOL'd when the Terms of Service came up and was scrolling at 1px per inch.
Re: User Inyerface – A worst-practice UI experiment
#255Earlier quoted context omitted.
I scrolled down and still couldn't see the checkboxes under the last row. Maybe it also doesn't work on Firefox, because as trivial as it is to make a site that works everywhere no one does. Normally this frustrates me, but if that's the case here it kind of makes sense.
The checkboxes are actually above all of the images. I tried scrolling down, realized I couldn't, then scrolled up to find the unfilled row at the top...
Re: User Inyerface – A worst-practice UI experiment
#256Re: User Inyerface – A worst-practice UI experiment
#257Re: User Inyerface – A worst-practice UI experiment
#258[SPOILER] since you have to tick all the boxes on the captcha page, this piece of code is actually faster to type in than to click everything: document.querySelectorAll(".icon.icon-check.checkbox__check").forEach(span => span.click())
More concise to use an attribute selector: 'input[type=checkbox]'.
Re: User Inyerface – A worst-practice UI experiment
#259Earlier quoted context omitted.
But how else could you make sure people knew your content was coming soon!?!
"Under construction" gifs of course!