Frederick Polgardy wrote: > Depends on what you need. IE7.js is brilliant if you want to bring > IE6 and 7 up to (mostly) modern DOM and event compliance. But you > don't need it if you're using something like Prototype or jQuery or > MooTools or <insert your favorite library here> because those > libraries will pave over those issues for you. Personally, big shout > outs to Dean Edwards for IE7.js. (There might even be an IE8.js out > already.) > > On Fri, Jun 6, 2008 at 7:46 AM, Michael Stephens <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Has anyone used this library. I'm not a fan but my co-worker is > trying to seel me on this. I would give him a definitive no if I > knew that no one else used it. > I've used it on two different projects. There is an IE8.js out. ( http://code.google.com/p/ie7-js/ ) It really is a beautiful and useful script. IMO the main use of it is to save time not worrying about coding to IE deficiencies, especially with CSS. For example, use li:hover, opacity, png images, and proper box modeling all you want; IE8.js will automatically fix it. It does a bang-up job. It isn't perfect on some of IE6's more complex bugs, but it always displays better than IE6 alone.
I find it to be a huge time saver and a really happy way to look forward to browser compliance. Spending half your time coding to and debugging for IE6 is not fun at all. - Ken Snyder --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
