←back to thread

137 points steventhedev | 1 comments | | HN request time: 0s | source
Show context
Garlef ◴[] No.43747430[source]
Hm. Either that page or the tech itself is not great on mobile.
replies(2): >>43747496 #>>43747961 #
ano-ther ◴[] No.43747496[source]
Takes a second or so to load on mine (iOS Safari). But then it shows correctly, even if the second diagram is a bit small (it fits in a quarter of the 1in circle).
replies(1): >>43747514 #
frumplestlatz ◴[] No.43747514[source]
It crashes (“a problem repeatedly occurred”) a few seconds after loading everything on my device (also iOS Safari).

I love tikz, but lightweight it is not; it’s not a huge surprise it takes a few seconds to render.

No idea what’s causing the crash, though.

replies(1): >>43747730 #
kccqzy ◴[] No.43747730[source]
Well iOS Safari is in general buggy and tends to display the "a problem repeatedly occurred" message on many other slightly heavy web pages. This web page shouldn't be blamed for causing Safari to crash.
replies(1): >>43747834 #
frumplestlatz ◴[] No.43747834[source]
Nobody is assigning blame, we don’t know the root cause.

I could just as easily say that Safari shouldn’t be blamed for a buggy website, but I’d be overreaching just as much as you just did.

replies(1): >>43747872 #
kccqzy ◴[] No.43747872[source]
By definition buggy websites that crash the browser are bugs in the browser.

It may have security implications, or it may not. It might just be an innocent case of someone using assertions instead of proper error reporting. Nevertheless it's a bug in the browser.

replies(2): >>43747904 #>>43749091 #
1. Jaxan ◴[] No.43749091[source]
It doesn’t crash, but tells me there is a problem. To me,this seems like a safe way to deal with buggy websites.