Post

Replies

Boosts

Views

Activity

Reply to WebKit PushStateFilePathRestriction
This is due to a change in WebKit (https://github.com/WebKit/WebKit/commit/78a55cf3976ce0b4543df42b03c335c5b89d27dd) to match the HTML spec with regards to pushState and file: URLs: https://html.spec.whatwg.org/multipage/history.html#can-have-its-url-rewritten If targetURL's scheme is "file", and targetURL and documentURL differ in their path component, then return false. (Differences in query and fragment are allowed for file: URLs.) So it's fine to use pushState with file: URLs to go from index.html to index.html#/dashboard, but it is not allowed to go from index.html to index.html/dashboard. Maybe your framework has an option to use hash-based URLs for routing? The other alternative would be to use a custom scheme to serve your content instead of file: URLs.
Topic: Safari & Web SubTopic: General Tags:
May ’23
Reply to WebKit PushStateFilePathRestriction
This is due to a change in WebKit (https://github.com/WebKit/WebKit/commit/78a55cf3976ce0b4543df42b03c335c5b89d27dd) to match the HTML spec with regards to pushState and file: URLs: https://html.spec.whatwg.org/multipage/history.html#can-have-its-url-rewritten If targetURL's scheme is "file", and targetURL and documentURL differ in their path component, then return false. (Differences in query and fragment are allowed for file: URLs.) So it's fine to use pushState with file: URLs to go from index.html to index.html#/dashboard, but it is not allowed to go from index.html to index.html/dashboard. Maybe your framework has an option to use hash-based URLs for routing? The other alternative would be to use a custom scheme to serve your content instead of file: URLs.
Topic: Safari & Web SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’23