Louis CAD
Louis CAD
You can check you are not calling `cancel()` too early. IIRC, I had that issue because I made a mistake in an extension where I was calling cancel after a...
Having an interceptor that rewrites the http 204 and 205 responses to 200 should work best.
Inspired from the snippet just above, I made a version that doesn't fail when the server responds with a content length of zero, and is lenient if there's actually some...
A webm or other looping autoplay video format would be lighter than ~JIFs~ GIFs and can still play in a WebView. That's my 2 cents.
`GloblaScope.launch` can be removed and just get the listener removal inside `withContext(Dispatchers.Main.immediate + NonCancellable)`. I think that's an acceptable solution until `callbackFlow` stabilizes.
@martinbonnin Why not just use `trySend` instead of risking blocking the thread, which is likely to be the main one?
Maybe the non main thread support could be dropped so the `synchronized` blocks could be stripped in favor of a low overhead main thread check?
From my tests, the quickest way to check for looper match is to cache (as a member) the thread of the looper and compare it with `Thread.currentThread()`. This means something...
This also raises the question of whether Looper thread enforcement is needed. Just checking the current Thread in the constructor could be enough, right?
@edvin Would you submit a draft PR (new GitHub feature released less than 24 hours ago) so we can subscribe to it and be notified when there's an update or...