For example VML is broken in many cases in IE8: If you are using percentage units or if the element has been created outside of the document (in a fragment for example) the element is not rendered. It has correct dimensions, correct attributes, but it is not displayed and there is no way to detect it. Feature detection doesn't work in that case and in some other, that's why $.browser.msie/opera/mozilla/version will always remain in jQuery, and that's why I think we should add a parameter that indicates when IE8 is in IE7 mode (VML works in that case).
On Mar 5, 8:24 pm, Matt Kruse <m...@thekrusefamily.com> wrote: > On Mar 4, 3:26 pm, lrbabe <lrb...@gmail.com> wrote: > > > I'm aware that jQuery promotes features detection over browser > > sniffing but currently we provide no way for the user to figure out > > easily when the browser is IE8 operating in the so called > > "compatibility mode". > > Why would you need to detect this? What problem are you trying to > solve? > > This is exactly why any type of browser sniffing is inherently error- > prone, and feature-detection strategies should be used instead. > > Matt Kruse --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
