5 ms·
Yeah, I'm interested too. I might be wrong, but AFAIK there aren't any specs on how a browser should implement forward/back buttons, right? I'm personally gett
by pcr910303 6y ago
Yeah, I'm interested too. I might be wrong, but AFAIK there aren't any specs on how a browser should implement forward/back buttons, right?
I'm personally getting a ton of mileage on the Safari's much more stable forward/back cache, the fact that you can go back reliably gives me more comfort than other browsers where going back usually refreshes the page (although I can't really explain how this is much better). I personally feel that this bug is more of a web app bug rather than the browser.
- capableweb 6y agoThe closest you get for how browsers should act regarding history is part of the HTML spec here: https://html.spec.whatwg.org/multipage/history.html https://html.spec.whatwg.org/multipage/history.html Of course, the exact implementation is not specified, browsers are free to either implement cached behavior, which I think Firefox does as well, or just a naive refresh.
- tinus_hn 6y agoI think the closest is the pagehide event https://html.spec.whatwg.org/multipage/browsing-the-web.html#event-pagehide https://html.spec.whatwg.org/multipage/browsing-the-web.html... Which appears to be supported in Safari, just like all the other browsers.
- gsnedders 6y agoThere's a metabug on HTML at https://github.com/whatwg/html/issues/5880 https://github.com/whatwg/html/issues/5880 about defining how various platform-exposed features behave in the face of a bfcache (backwards/forwards cache).