Safari Fetches Sources Twice in MacOS #13

New issue

Open

opened 2024-07-03 15:11:36 +00:00 by ThePerfectComputer · 0 comments

ThePerfectComputer commented

2024-07-03 15:11:36 +00:00

(Migrated from github.com)

We should ideally look into a way to resolve this long-term(see attached image).

Also, a snippet from Discord conversation with Martin:

About the loading wasm modules - there is a script with preload attribute in the HTML header to start downloading wasm/js/whatever as fast as possible so it'll start almost immediately and then when the browser sees the link again in the HTML body then it just says "aha, I'm already downloading it or downloaded it, I don't need to download it again!". But if the delay between that preloading and reading the actual script to load the file is too long or if there is a bug (I wouldn't be surprised if there is one in Safari) then it may behave a bit differently. Also I can imagine it may me a bit more reliable when it's built in release mode because of smaller size and faster processing.

We should ideally look into a way to resolve this long-term(see attached image). Also, a snippet from Discord conversation with Martin: > About the loading wasm modules - there is a script with preload attribute in the HTML header to start downloading wasm/js/whatever as fast as possible so it'll start almost immediately and then when the browser sees the link again in the HTML body then it just says "aha, I'm already downloading it or downloaded it, I don't need to download it again!". But if the delay between that preloading and reading the actual script to load the file is too long or if there is a bug (I wouldn't be surprised if there is one in Safari) then it may behave a bit differently. Also I can imagine it may me a bit more reliable when it's built in release mode because of smaller size and faster processing. ![image](https://github.com/JoyOfHardware/FastWave2.0/assets/103011002/58408c8f-dcbb-4416-bc58-95826197e584)