Arman Nisch

Thank you, @lbragile @james-reed-toshi @Lornz- combining your three solutions produced the results. Wow, what a ride. Specifically, these three answers were key: 1) https://github.com/styled-components/styled-components/issues/3607#issuecomment-1000937952 2) https://github.com/styled-components/styled-components/issues/3607#issuecomment-1002538757 3) https://github.com/styled-components/styled-components/issues/3607#issuecomment-1003629265

Ok, but what about this scenario: what if a frontend might be waiting for a computationally heavy response form the server, then and for some reason the frontend is disconnected...

I have a similar issue occurring now, but it only seems to affect the `` HTML Element. I do have a css class assigned to my `` element, but it...

@shilman can one reopen this issue? Its not resolved and does have some direct side-effects that affect how our applications behave.

@matthewhampton haha, ok, this is so obvious in hindsight. Thank you for picking up on this. @shilman an overengineered idea might be to add a painfully obvious disclaimer on the...

Status? Been a while now....

I can confirm I am also seeing this behaviour. It's actually any number that one types after 100 with x. So type 100, wait two seconds, type **1**, then one...

Any update on this? :)