I see the same situation and response have previously been repeated in several other threads concerning different websites.
It’s quite understandable that some web content would not render well in some browser. But crashing the app is a significant escalation.
When Safari crashes, I would immediately suspect there’s something wrong with the website I just navigated to. DT, on the other hand, is not a dedicated web browser. It will take multiple crashes (or a tedious support ticket) before the user could even have a chance to realize they shouldn’t open certain “bombmarks”.
That’s just disastrous UX. We’ve had multiple posts here lamenting that DT crashes often. I suspect those experiences have something to do with the “bombmarks”. A hundred such bookmarks in a database, and you are playing the good ol’ Minesweeper game. Yay!
I hope “incompatible web technologies” do not crash or beachball the entire program. Blanking the tab, for instance, is a much better indicator of incompatibility.
Crash-only programming is definitely easier than crash-proof programming, and you hardworking guys don’t have the resources to cover everything. Still, something to prevent the “bombmarks” from exploding upon clicking would be desirable.