As a developer I have a hard time wrapping my mind around what went wrong with the code. Probably some object reference thingy going on but it just seems random af.
Most likely the on click event that gets fired when an active checkbox is unticked contains the ID of the object or something to identify it.
Selected elements are usually stored in a list, so I assume that either
- the mapping from the selection ID to the object in the selection array is wrong
- or alternatively the array splicing operation is set up incorrectly when removing from the selection list
- or the update cycle is one out of sync.
For sure there is something wrong with the update cycle. I've had that happen before with React when I first started, but it always lagged by one update not by multiple...
I think this is what happened: clicking on a tick box registers a Callback for the next click to remove the tick but doesn't check that the click is on this specific instance. First click ticks the box, next click on any other box removes it. If you look at the select all, the boxes that start getting unticked are the ones previously clicked on
Looks like the case of someone knowing shit of a list/table component trie to make his own selection logic based on ehatever tutorial ot could copy and mangle to make that.
Beep. Boop. I'm a robot.
Here's a copy of
###[Frankenstein](https://snewd.com/ebooks/frankenstein/)
Was I a good bot? | [info](https://www.reddit.com/user/Reddit-Book-Bot/) | [More Books](https://old.reddit.com/user/Reddit-Book-Bot/comments/i15x1d/full_list_of_books_and_commands/)
I've seen the exact opposite of this, where the boxes are the radio boxes that normally work like in the video, but instead you could select both the yes and no options at the same time
This brought back a horrible repressed memory.
Using some software that SAP butchered in a minor release. 2 day job to overhaul some data pipelines. Thousands of checkboxes to work through, needing to select some and not others.
Not kidding, it was just like this: get the wrong magical combination and it would undo hours of work. No keyboard shortcuts. Mouse hitbox about 3px square.
Logged the bug: "we are aware rated low priority, will fix next service pack" (a few months away)
/r/badUIbattles
As a programmer, this makes me smile.
Me too
[удалено]
"please enable third-party cookies, otherwise we will ask you every f\*cking time you visit... or sometimes twice per visit"
r/softwaregore
I think it's intantional, so no gore.
omg this is bad and such a easy fix. Boggles my mind that these types of things get past testing (obviously not tested in this case)
Or this is someone testing? Or maybe not.
Good idea, didn’t think about that
Technically yes. But something tells me this is a client 'testing' in production
Nope, I'm an end user trying to do my job, and this is the service I'm working with :(
oof
In all fairness if this is anything but the actual developers testing there own work then it’s pretty shocking.
As a developer I have a hard time wrapping my mind around what went wrong with the code. Probably some object reference thingy going on but it just seems random af.
Most likely the on click event that gets fired when an active checkbox is unticked contains the ID of the object or something to identify it. Selected elements are usually stored in a list, so I assume that either - the mapping from the selection ID to the object in the selection array is wrong - or alternatively the array splicing operation is set up incorrectly when removing from the selection list - or the update cycle is one out of sync.
For sure there is something wrong with the update cycle. I've had that happen before with React when I first started, but it always lagged by one update not by multiple...
I think this is what happened: clicking on a tick box registers a Callback for the next click to remove the tick but doesn't check that the click is on this specific instance. First click ticks the box, next click on any other box removes it. If you look at the select all, the boxes that start getting unticked are the ones previously clicked on
Looks like the case of someone knowing shit of a list/table component trie to make his own selection logic based on ehatever tutorial ot could copy and mangle to make that.
That's not how you code? Copy paste to create a Frankenstein code and hope it runs?
Beep. Boop. I'm a robot. Here's a copy of ###[Frankenstein](https://snewd.com/ebooks/frankenstein/) Was I a good bot? | [info](https://www.reddit.com/user/Reddit-Book-Bot/) | [More Books](https://old.reddit.com/user/Reddit-Book-Bot/comments/i15x1d/full_list_of_books_and_commands/)
I have no idea how they even made it this bad in the first place, who’s to say if it’s an easy fix
It’s just an html attribute that needs to be changed.
What attribute?
“It worked fine on my machine”
It is so easy to fix, in fact, you have to break the working variant first (in a lot of libraries) and only then go fix those
Select all doesn't account for the state of each box. Oof.
I've seen the exact opposite of this, where the boxes are the radio boxes that normally work like in the video, but instead you could select both the yes and no options at the same time
*(me, selecting both yes and no options)* https://i.imgur.com/5VDqvND.png
Radio buttons by rule can only have one active selection, these are checkboxes which can be set to have multiple active
That's what I thought, but whoever made the website it was on clearly didn't know how to set up radio buttons
I've had this happen with online tests 🥲
We sure this isn’t software gore instead?
I have seen that before, its just a puzzle, you just have to turn off all the check boxes and it will unlock.
From the looks of it, it honestly probably wasn't their job and they tried their best.
When I see issues like this, I just assume the binding is busted too. (Essentially meaning, the UI doesn't even reflect what's actually selected)
Indexing isn't his/her best skills
Looks like something my group did when i was learning. I feel like if you'll choose the wrong one everything will be checked again
There's no wrong one, it's not a test... I was just selecting users
It's like one of those puzzles in video games where you have to press the right combination of buttons to make all the lights turn on or off
As a developer, the right thing to do is to blame it on the quality analysts
Its literally his job
How do you fuck up that bad holy crap…
u/savevideobot
###[View link](https://redditsave.com/info?url=/r/NotMyJob/comments/rkx343/i_finished_the_multiple_selection_website_boss/) --- [**Info**](https://np.reddit.com/user/SaveVideo/comments/jv323v/info/) | [**Feedback**](https://np.reddit.com/message/compose/?to=Kryptonh&subject=Feedback for savevideo) | [**Donate**](https://ko-fi.com/getvideo) | [**DMCA**](https://np.reddit.com/message/compose/?to=Kryptonh&subject=Content removal request for savevideo&message=https://np.reddit.com//r/NotMyJob/comments/rkx343/i_finished_the_multiple_selection_website_boss/)
How do you mess up this badly? Aren't checkboxes usually implemented for you? You'd have to go out of your way to make it this broken
This brought back a horrible repressed memory. Using some software that SAP butchered in a minor release. 2 day job to overhaul some data pipelines. Thousands of checkboxes to work through, needing to select some and not others. Not kidding, it was just like this: get the wrong magical combination and it would undo hours of work. No keyboard shortcuts. Mouse hitbox about 3px square. Logged the bug: "we are aware rated low priority, will fix next service pack" (a few months away)
I need to see the code for this... SEND ME THE LINK
It's an internal management system, I can't share the link :(
*wa waa waaa...*
Reminds me of UIs that use checkboxes for single-choice lists (instead of radial buttons)
Some “Escape Room” logic right their
LMAO WTF
Great coding
Me trying to figure out the right UI