Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> One especially crazy seeming one from today's perspective is that there's a separate implementation of event propagation, I believe because because it dates back to browsers that only implemented one half of event bubbling/capture!

My oh my, that takes me back to the days of quirks mode and early versions of Internet Explorer. I made a good living through college helping design and ad agencies backport stuff to IE5/6/7 and became intimately familiar with the lack of event bubbling support and fan favorites like:

1. IE displaying a blank page with no errors whenever a CSS file of more than 4kb was loaded

2. Resolving CSS rendering issues between IE5/6/7 due to differing rendering strategies for the CSS box model

3. Debugging javascript in IE back when dev tools didn't exist.

For all people harp on the current state of the web, we have come a long, long way.



> IE displaying a blank page with no errors whenever a CSS file of more than 4kb was loaded

This must predate IE5 right? I’m absolutely certain I was shipping larger single CSS files without hitting this.


I may be misremembering the file size (8kb? 32kb?), but I distinctly remember this being the bane of my existence for IE6.

EDIT: my memory was faulty—I was conflating two bugs:

1. Certain CSS expressions on html or body tags could cause pages in IE6 and 7 to crash

2. In IE6, the browser would happily parse large CSS files until ~288kb of CSS had been parsed and applied. Any remaining CSS would be silently ignored and discarded. See: http://joshua.perina.com/africa/gambia/fajara/post/internet-...


This sounds a lot more familiar! Good find.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: