You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
In iOS brave it seems like we don’t get a progress bar until the first byte of the HTML response has been received. This is different from Safari, where you get the initial ~10% of the progress bar filled once the request has been issued. To my experience, the Safari approach feel nicer, since if you’re in a really slow network situation, clicking on links seems to do nothing at all for a while, making it seem like the browser has locked up.
The text was updated successfully, but these errors were encountered:
Since `WKWebView.estimatedProgress` is a Double, the cast to a `Float` was failing when the value was 0.1 for unknown reasons. Most likely something to do with the bridging between `NSNumber` and `Float` when the underlying value stored in the `NSNumber` is a `Double`
Since `WKWebView.estimatedProgress` is a Double, the cast to a `Float` was failing when the value was 0.1 for unknown reasons. Most likely something to do with the bridging between `NSNumber` and `Float` when the underlying value stored in the `NSNumber` is a `Double`
Description:
Link: https://bravesoftware.slack.com/archives/C06UXF3KJ/p1622509944112800
The text was updated successfully, but these errors were encountered: