Tags are actually borked to all hell.
-
Try to add a tag before selecting a category.
Also, try scrolling when you have the tag suggestions open.
-
@jazzyjosh said in Tags are actually borked to all hell.:
Also, try scrolling when you have the tag suggestions open.
Never tried that before WHAT THE ACTUAL FUCK IS GOING ON
-
@raceprouk position isn't set to fixed.
-
@jazzyjosh said in Tags are actually borked to all hell.:
@raceprouk position isn't set to fixed.
Seriously. I wish web would catch up to desktop app.
-
Also a choice quote:
@coderpatsy said in Canary Tests:
@lorne-kates The only thing I can think of is category-specific restrictions on tags. Which then if you can't enter tags without the category, that needs to be conveyed to the user before they try to enter tags.
-
So, a popup instead of deleting the text
Pick a category, bitch!
But seriously, could we change the input suggestion text to ask for a category selection.
-
@xaade said in Tags are actually borked to all hell.:
So, a popup instead of deleting the text
Pick a category, bitch!
But seriously, could we change the input suggestion text to ask for a category selection.
I wonder if I can intercept it and just pretend the user is always in General like I did for uploads.
-
@xaade said in Tags are actually borked to all hell.:
So, a popup instead of deleting the text
Pick a category, bitch!
Oh, here's a fucking idea-- don't validate the category when entering information in a field not related to category.
Fucking hell, why can't webdevs figure this out. How many fucking times have I had to scroll halfway up a form, because when I picked my country (and thus reloaded the state/province box), it fucked off an tried to validate my first name/last name which hadn't been filled in yet, because I was picking my country/state first because that always fucks things up.
The "Is Category Null/Empty" check should only fire on:
- Category dropdown onchange (to see if someone switched it back to blank)
- Form submit
That's fucking it.
FUCK.
-
@lorne-kates Why don't you just not live in Canada? Sounds simpler.
-
Everywhere I go I have to point out that cross validation should occur on submit only.
I worked for a company that wouldn't let you leave a subset of fields if it didn't validate.
"Oh shit, I misspelled my name"
"Too late, you entered month and not day. You're stuck here! Mwa ha ha ha"
-
@blakeyrat said in Tags are actually borked to all hell.:
@lorne-kates Why don't you just not live in Canada? Sounds simpler.
Given some of the sites I've tried to submit forms for, you're not far from the truth.
(Though, tobe faire, most of them have a blank state/province field, so the same issue happens with picking USA)
-
@xaade said in Tags are actually borked to all hell.:
"Too late, you entered month and not day. You're stuck here! Mwa ha ha ha"
You're stuck here! – 00:30
— underbird
-
@xaade said in Tags are actually borked to all hell.:
cross validation
So THAT'S what that flavor of bullshit is called. Thanks.
-
It's ok to have it, but don't affect input while they're entering fields. Red flag fields and let them continue.
-
@xaade said in Tags are actually borked to all hell.:
Everywhere I go I have to point out that cross validation should occur on submit only.
I worked for a company that wouldn't let you leave a subset of fields if it didn't validate.
"Oh shit, I misspelled my name"
"Too late, you entered month and not day. You're stuck here! Mwa ha ha ha"
A site I maintain has workflows that go through a few pages. When you try to go to the next page, it validates and won't let you past if there are any issues. Fairly standard.
Unfortunately, it also validates if you try to go back to the previous page. So if you realise just after loading page 3 that you made a mistake on page 2, you need to fill in everything that's required on page 3 before going back to fix it. Depending what you change on page 2, some of that information may not even be relevant afterwards
-
@jaloopa said in Tags are actually borked to all hell.:
@xaade said in Tags are actually borked to all hell.:
Everywhere I go I have to point out that cross validation should occur on submit only.
I worked for a company that wouldn't let you leave a subset of fields if it didn't validate.
"Oh shit, I misspelled my name"
"Too late, you entered month and not day. You're stuck here! Mwa ha ha ha"
A site I maintain has workflows that go through a few pages. When you try to go to the next page, it validates and won't let you past if there are any issues. Fairly standard.
Unfortunately, it also validates if you try to go back to the previous page. So if you realise just after loading page 3 that you made a mistake on page 2, you need to fill in everything that's required on page 3 before going back to fix it. Depending what you change on page 2, some of that information may not even be relevant afterwards
If the pages don't commit anything until they're all filled in, then only validate on the last page, and use tab control as a navigation tool to indicate which has the error.
-
@jazzyjosh https://github.com/NodeBB/NodeBB/issues/5938
I have a vague feeling that it is the way it is because raisins. Something with mobile... or IE... maybe Safari... or Safrai on Mobile.
In any case it's also an upstream lib but we'll take a look.
-
@julianlam This was on Chrome. Unless you mean it was written this way to fix a defect.
-
Right, I mean some workarounds to make the element work properly in those aforementioned browsers might break in newer browsers because of how we use it.
Namely the composer itself is a fixed element (to the bottom of the viewport), and this is a fixed element affixed to another fixed element.
-
@xaade said in Tags are actually borked to all hell.:
@jazzyjosh said in Tags are actually borked to all hell.:
@raceprouk position isn't set to fixed.
Seriously. I wish web would catch up to desktop app.
I am currently about one incident away from scrapping the WtfFramework Command and Control interface web app and rebuilding it in WPF.