2 ms·
It isn't like WebKit is intentionally doing IE6-ish things, it's just that any rendering engine will have certain bugs. Developers try to work around these bugs
by keeperofdakeys 14y ago
It isn't like WebKit is intentionally doing IE6-ish things, it's just that any rendering engine will have certain bugs. Developers try to work around these bugs, and if their is only "one" implementation, they'll start relying on its quirks. A good example in C would be storing a pointer in an int. It made perfect sense at the time, and it allowed people to be lazy. However it doesn't make any sense these days.