The X just sends a signal to your application. If you ignore that signal, it will just do nothing.
That signal tells your application to clean itself. Maybe the changed how that “cleaning itself” worked, in a way that lead to actually ignoring the signal all together.
The thing is easy to break. The question is how that even got past QA testing. Or even just any other dev testing.
A single person launching the program and trying to close it should see the bug.
oh it wasn’t ignored, it gave you a generic error message when you clicked it :D
yeah that’s what i mean, how do you break something so obvious and then just make that version live globally. it took them a day to fix it, even if an intern did it it should’ve been fixed in minutes
throwback to that one update that somehow managed to break the “X” as in, the button that closes the software. how do you even break that???
The X just sends a signal to your application. If you ignore that signal, it will just do nothing.
That signal tells your application to clean itself. Maybe the changed how that “cleaning itself” worked, in a way that lead to actually ignoring the signal all together.
The thing is easy to break. The question is how that even got past QA testing. Or even just any other dev testing.
A single person launching the program and trying to close it should see the bug.
oh it wasn’t ignored, it gave you a generic error message when you clicked it :D
yeah that’s what i mean, how do you break something so obvious and then just make that version live globally. it took them a day to fix it, even if an intern did it it should’ve been fixed in minutes