zmarn

4 ms·

1. 1.▲
   by zmarn 14y ago

   Ok, I narrowed down what kills Chrome. minimalist example: data:text/html;charset=utf-8,<p style='font-family: "Times New Roman";'>%D9%88%20%D2%88%D2%88%D2%88 It seems to be a problem with utf-8 vs. unicode + Times New Roman
2. 2.▲
   by zmarn 14y ago

   After reducing the html-code in the site, it seems to me that it is not the title that causes the crash, but the p-tag with the specific css-style applied.
3. 3.▲
   by zmarn 14y ago

   Really interesting, played around with it locally and it just kill two random neighboring tabs, while not effecting others. Chrome 24.0.1312.57 | OS x 10.8.2
4. 4.▲
   by zmarn 14y ago

   you should probably disable user-facing raw php-errors in a production environment (just my opinion) http://themefurnace.com/wp-content/plugins/hello.php