Notice I didn't overwrite old versions, I changed the file names. All 3 versions are still there.
I just check for IE and remove and re-add the style element instead of changing the contents of it like I do for everything not IE. I think most all of us are sympathetic to IE issues as most of us are working on sites that have to work with it. I've only really had 3 run-ins with IE (mainly IE6): tweaking stuff in the head (like scripts and styles), PNG alpha transparency (which I now address server side instead of client side), and layout inconsistencies. For my particular application, we've decided to accept JavaScript as a requirement, which has improved our quality of life immensely. As a result, we now use Ext for layout, and it works beautifully. So, so much better than keeping different versions of style sheets all over the place in a feeble attempt to keep our (admittedly complicated) layout consistent across browsers. Good luck with it. --Erik On 8/25/07, Pops <[EMAIL PROTECTED]> wrote: > > Outstanding Erik! Don't blame yourself. We all naturally do the same > thing. :-) > > Ok, I didn't save your first version. What did you change in your old > version to this one? > > We desperately need to know all jQuery concepts that are sensitive to > IE. > > We are a commerical product vendor with a web server so, hate it or > not, our corporate customers will have a majority IE base. I just > had a conversation the idea day with Chucky Cheese IT manager and we > were talking about this. He didn't need to remind me. No excuses. FF > is nice and desirable on a person to person basis, but IE is still #1 > consideration on a corporation basis. Thats the same across the > board. I love jQuery and want to use it but I am continueing to see > far too many IE issues either cosmetic or just doesn't function as I > keep working with jQuery or even try other people's plug-ins code. > > I hope JR gets to chance to see this thread. jQuery is taken a life on > its own, even if its its "night work", to really grab the market > place, IE must be supported 100% or just as well as it works under FF. > > Possible a special section in the docs dedicated to compatibile issues > need to be section off. With this, people can help in resolving them > with patches and update suggestions. > > -- > HLS > > On Aug 25, 2:58 am, "Erik Beeson" <[EMAIL PROTECTED]> wrote: > > That's what I get for not testing IE6 with my more complicated example > > :) I'm not surprised that IE has issues with this. Creating dynamic > > script tags has been an issue too. IE seems to have a lot of trouble > > modifying stuff in the head. Here's a version that works on IE, FF, > > and Safari: > > > > http://erikandcolleen.com/erik/projects/jquery/cssinject/cssinject3.html > > > > --Erik > > > > On 8/24/07, Pops <[EMAIL PROTECTED]> wrote: > > > > > > > > > Right, I just got it to work too. But I was still at 1.1.3.1 so I > > > had to call evalScripts(). > > > > > Let me try your script and mine under IE 6.0 > > > > > Ok, your script gives as soon as you type: > > > > > Error: Unexpected call to method or property access > > > > > and with the my button version, I don't see an IE error but it isn't > > > "evaluated'. > > > > > Guys! I am seeing for too much IE browser issues. Where is the "Cross > > > broiwser" support claim? jQuery seems to only really well work with > > > FF. Is this just one of few instances of IE problems? > > > > > -- > > > HLS > > > > > On Aug 25, 2:18 am, "Erik Beeson" <[EMAIL PROTECTED]> wrote: > > > > And here's a version that has live updating: > > > > > >http://erikandcolleen.com/erik/projects/jquery/cssinject/cssinject2.html > > > > > > Tested of FF and Safari. I'm not motivated enough to boot up Parallels > > > > to test IE. It seems like it works just like one would expect it to. > > > > Quite frankly, I'm a little surprised that it does. > > > > > > --Erik > > > > > > On 8/24/07, Erik Beeson <[EMAIL PROTECTED]> wrote: > > > > > > > Right, I just noticed that I forgot to put head in quotes. Here's a > > > > > little test page: > > > > > > >http://erikandcolleen.com/erik/projects/jquery/cssinject/cssinject.html > > > > > > > Works in FF2/Mac, Safari 2.0.4, IE6. > > > > > > > --Erik > > > > > > > On 8/24/07, Pops <[EMAIL PROTECTED]> wrote: > > > > > > > > On Aug 25, 1:31 am, "Erik Beeson" <[EMAIL PROTECTED]> wrote: > > > > > > > This seems to work in FF2/Mac: > > > > > > > > > var myCss = 'p { border: 2px solid #faa; }'; > > > > > > > $(head).append('<style type="text/css">' + myCss + '</style>'); > > > > > > > > I tried something like this, but it didn't seem to take. > > > > > > > > I drifted into doing something with the <link> in DOM that I see > > > > > > with > > > > > > FireBug. I figure if Firebug allows you edit it, you can program it > > > > > > too. I figured I can change what wast imported by overwring it with > > > > > > the content in the textarea. > > > > > > > > Anyway if it worked for you, it should work for me. Lets try it.... > > > > > > It > > > > > > didn''t take, but I do see it in DOM. Does it need to be "eval()"? > > > > > > > > -- > > > > > > HLS > >
