I get your point about this not being friendly, but solving it this way creates unnecessary crust in your application. That's kind of a similar problem.

So really you're overcomplicating an application to solve an issue that probably not much end users are noticing. Should you then really add it to your best practises template app? I don't consider this workaround a good practice, I'd even go as far as calling in bad practice.

@sexybiggetje It’s a temporary workaround until the actual issue is fixed in the OS.

@sexybiggetje I haven’t decided whether or not to include it yet. I’m waiting to see if the issue is tackled/solved first.

Sign in to participate in the conversation
Aral’s Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!