can't believe we're still designing components that break when the user closes the tab. fix the bug, not the bandaid solution. make it work when the tab is closed.

ikr? like maybe actually test for that case instead of just catching the error.

fr, that's the real issue. can't keep slapping on temporary fixes. we need to build stuff that actually holds up

are you kidding me, that's not a bug, it's a feature, users expect it to stop running when they close the tab, get over it

are you kidding me? redesigning a whole page structure just so it doesn't lose unsaved work when

lmao yeah no kidding. also can we please just persist user data on page reload while we're at it

mate, that's a proper state of affairs. absolute shambles when stuff breaks like that.

what, do we not have the budget for that or something?

You're so right. That's a huge pet peeve of mine. Devs need to build in error handling and graceful degradation.

that's the problem with modern web dev, everyone just wants to slap on a react lifecycle hook and call it a day. how about we just disable the internet when the tab closes? that'll fix it.

what do you expect, this is javascript we're talking about. if you want it to work when the tab is closed, use service workers or something.

fr, how tf do you mess that up? devs need to stop being lazy and actually fix the core issue. what's the point of even shipping that?

so how do you plan on storing all that state then?

yeah exactly, seriously who signs off on something like that. wouldn't even pass a quality check in our project team. holy cow

Are you kidding? Closing tabs is the new exit button. Just assume it's gonna happen and design around it. Don't fight the users' habits.

are you saying this because of a recent project or is this just a general vent

How about we focus on why users feel the need to close tabs in the first place?

hate to break it to you. But sometimes a bandaid is the best we can do.

yeah, that's the real issue. if the component can't handle basic lifecycle events. It's not ready for production.

that's a gross oversimplification - business requirements demand the "bandaid" in many cases. damned customers would still be furious if their purchasing cart expired when switching to another tab.

ya really think a fix is that easy?

come on, that's just not how people use the web, most people don't care about your app still

for real tho, i'm sick of that bandaid crap. like just fix the damn problem instead of throwing a temporary solution at it.

u think the designers have just been sitting around twiddling their thumbs while devs are just slapping bandaid solutions on all day?

um, clients aren't always abt deepest browns and curls fixes, sometimes we gotta ship what we got

bruh who designs that trash? back to the drawing board, devs.

nah that's a terrible take. sometimes we can't control when the user closes the tab.

seriously, how hard is it to handle page unloading properly? this should be basic stuff, not a "workaround".

Tab-ling the issue until later

are you seriously suggesting a full redesign just for edge cases like tab closure?

i'm lowkey shocked it took this long for someone to point out the obvious.

preach!! can't stress this enough. and while we're at it, can we pls also stop assuming everyone

you really think that's an easy fix? do you have any idea how much work goes into making a web app? there's gotta be tradeoffs. You can't just wave a magic wand and make everything perfect.

I hear you, that's a real pet peeve of mine too. It's like the devs are just trying to cover their butts instead of actually solving the underlying issue.

i mean, it's not that hard to persist state properly, but at the same time can we please just make it so that people

Isn't that just a symptom of the whole throwaway tech culture we're living in? Shouldn't we be designing things to last instead of just patching them up to limp along?

Preach! And let's be real, if we're not thinking about edge cases, we're not doing our job. ship it when it works, not just when it looks good

preach. and can we also make it work on a slow connection, 10yr old phone, and with noscript enabled while we're at it?

lol sounds like someone needs a refresh

are you kidding me? that's a feature, not a bug. users are literally asking for this. it's not our job to babysit their browser usage.

ugh, seriously. that's such a pet peeve of mine. like, how hard is it to make it actually work?

Are developers on these projects even testing how real people use their apps?

right?! it's 2023, we should be able to handle that. and while we're at it, how about we make sure the app works offline too?

lmao 'make it work when the tab is closed' sounds like a sound life advice tbh

fr, how hard is it to make shit actually work. like, you're the dev, do your job.

omg yes. and also can we please fix the whole "refreshing the page wipes all your progress" thing while we're at it

totally agree. i'm fixin to see some refactoring on this before it's released, not just another hack to silence user

to simplify it even further: user closes tab, they're not doing it out of spite, let's not assume the worst.

that's a good point. how do you handle long-running tasks and asynchronous operations in your apps? i'd be curious to hear your approach.

same, it's wild how often this still comes up... and can we also talk about how it should just work

How do you propose we handle persistent storage then, or are you expecting users to just never close their tabs?

Probs the web always struggles with this, but at least we're pointing out the obvious. The real question is when will browsers start handling this properly so we don't have to live with these hacks?

i've come up with a solution - tab-shrink: it just gets smaller when you close it, no pun intended

I'm so down for this, but let's also acknowledge that sometimes this stuff is a result of complex dependencies and poor documentation from upstream providers, not just a simple

Haha, seriously! Closing the tab should be the ultimate test of application resilience. I'm picturing a software engineer frantically chasing a user around their house.

are you kidding me? it's 2023 and you still think every problem needs a from-scratch solution?

how tf were we supposed to know that users would actually close the tab?!

dude you're literally making me wanna go back to debugging my nana's msn messenger account. give me a break.

are you kidding me? we're a web3 company not a chromium development team. users closing tabs is not our problem to solve

preach. also can we please fix the one where it breaks when you refresh the page? that one's been driving me crazy

Clearly the real bug is the user being considerate of tab usage

aint that just like designin a porch without a roof, fixin to make it look purty but it's still gonna get wet in the

ugh yes, this drives me crazy. they need to actually fix the root issue instead of just slapping on a temporary fix.

Are you really advocating for a full rewrite of the underlying architecture or just expecting the developers to magically make it work with a few tweaks?

nice try, but we both know the user was never supposed to close the tab in the first place. if they wanted to keep using the app, they should've just never stopped.

tf you expect software to work when the tab is closed? thats some entitled bullshit.

um did anyone actually test the bandaid solution or are we just going to wing it and hope it sticks?

how's that supposed to work when the browser ain't even runnin' no more?

that's so dumb. maybe the user shouldn't have closed the tab before the component finished loading.

yeah because we clearly have the development skills of a middle schooler trying to fix theiritraffic jam in mii(rpway

yeah that's facts. if the code can't handle a user bouncing out, it's not really ready for production.

are you serious? you think it's that easy to just "make it work" without breaking other stuff?

not everyone can redesign their entire component from the ground up just because it doesn't work in

same energy when i'm trying to adult and my tab is still open on the beer delivery website

fair play, but have you met our users? they'll find a way to break it no matter what

then what's the right way to handle that case? would love to hear your thoughts.

Ah, the classic "tab closed, app broke" dilemma. I guess we're all just beta testing the latest features - "surprise tab shutdown" and "instant app meltdown"!

why are you still shipping broken features? it's 2023, time to get it right.

Are you kidding me? We can't force users to close their tabs a certain way. That's not how design works.

Totally agree, we're not investing enough time in architecture for a user experience. Let's focus on designing products that keep up with real-world user behavior, not just patchwork fixes. Only then can we truly claim to be innovating.

guess you just triggered the functionality to remind me that i still have to do that one thing i put off for 2 weeks

How is your engineering team prioritizing stability and reliability over new features? Closing a tab shouldn't break the app.

how hard is it to properly handle tab close events? js 101 stuff, no excuse for that bug.

yeah, that's a real head scratcher. how about we just make the entire app one giant popup that follows you around the screen? problem solved!

how about we just close the tab before the bug can break anything? problem solved!

ikr? its so frustrating. like just do the bare minimum and make it actually work.

are you seriously expecting devs to magically figure out when someone will click the x button on a page? that's user error, not a bug.

fr, it's unacceptable. just do it right the first time instead of half-assing it. there's no excuse for that level of incompetence.

for real, that's so annoying. why tf do people keep messing that up?

that's a dumb take. sometimes you gotta put a bandaid on stuff. not everything can be perfect right away and learn to deal with it.

are you suggesting our development team is just slapping together quick fixes instead of doing actual work?

Couldn't agree more. And while we're at it, can we also talk about how this same principle applies to offline mode? Users shouldn't have to worry about their work disappearing just because they lost signal for a sec.

who's writing this shit and does anyone tbh test this code

bruh, does your user excel at rock concerts or something?

aye, preach! plus, how many of us are still using ie6 at work?

imagine thinking that's a bug and not a feature. keep your damn tabs open if you want your shit to

have you run this by the team that has to meet the shipping deadline next week?

Totally agree, it's time to get rid of the "just enough" solutions. My model suggests that if we're solving the bug correctly. We should also redesign the system to prevent it from occurring in the future, not just patching it after it breaks.

We've been prioritizing 'd user experience' over actual functionality for decades, what makes you think that's gonna change now?

omg yes!!! and while we're at it, can we please kill the 'oops, you closed the tab, reload it for us?' prompt? just restore the damn state already

lol what's next, expecting our code to work when the wifi is off?