It does seem like a good example of why browser detection is a loser. I wouldn't suggest trying to paper over $.browser.version, it would be better to show it as 8 and let people fix their code as they find situations where version detection doesn't work.
The biggest change that I have seen is that setExpression is no longer supported in css. That has been used by several plugins to work around IE6/7 bugs, I can only hope that the bugs were fixed in IE8. Has anyone seen a comprehensive list of what has changed from IE7 to IE8? I have been triaging jQuery bugs for a couple of months now and can tell you that most of them have the same behavior on both IE7 and IE8. At least it's easier to diagnose them with the IE8 built-in debugging tools. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
