3 ms·
Hilariously it does not throw that warning if viewed in Chrome on iPhone, even though Chrome on iPhone just uses a slower version of the Safari rendering and Ja
by snowwrestler 12y ago
Hilariously it does not throw that warning if viewed in Chrome on iPhone, even though Chrome on iPhone just uses a slower version of the Safari rendering and JavaScript engines.
In fact on my iPhone, the page ran fine in mobile Safari, but completely bogged down in Chrome.
This is one example of why browser sniffing is not a great way to determine the actual capabilities of a browser.