5 ms·
You need just to add a meta attrib, no big deal: <meta http-equiv="X-UA-Compatible" content="chrome=1">
by js4all 16y ago
You need just to add a meta attrib, no big deal:
<meta http-equiv="X-UA-Compatible" content="chrome=1">
- tnorthcutt 16y agoI understand it's not much, but isn't the whole point of standards that you can do things one way, and it works, without any little "no big deal" changes?
- wccrawford 16y agoYes, and if you could get everyone to follow them, this hack wouldn't be needed. Until then, you can use this to provide a better experience for customers that have a standards-compliant browser (or one that can use the hack) and provide a lesser experience for the rest, and that should be easier (and provide a better experience) than trying to make everything work on all browsers.
- tnorthcutt 16y agoRoger that. I guess I just wanted to say out loud that effort still needs to be put towards moving people to standards-compliant browsers.