Correct. It's a bit annoying to have to have different preloading implementations for Chrome vs Safari though. For ease of use, we just stick with doing preloading client side for now.