weedpacket. THANKS.. that's what i was looking for. I never quite got the syntax right from the examples i found.. none of them did quite what i was looking for. Ill let you know if it works 😃

    Basically the problem with migration of JS apps from IE to non-IE browsers is:

    • The IE DOM, which works by putting any object with an ID into the "window" object under the same name - or does it ? I assume that it avoids clashes with predefined things.

    This means, when you migrate FROM IE, code which makes the assumption that all browsers do this, needs to be changed.

    Typically we use document.getElementById() to get elements by ID, but it's not the only way of obtaining things.

    The problem with migrating TO IE, is exactly the same. Say I want to use a variable attached to the window object, called "score" (for my game), and I happen to have an element in the page with an ID of "score" - that's no good, as IE will overwrite my variable with the page element, causing my application to fail.


    Obviously there are other gotchas with IE, mostly with its incorrect interpretation of CSS. For example:

    • Impossible to override certain built in styles by using "inherit" values for things
    • Incorrect interpretation of many box properties, specifically padding:auto, but also other stuff.

    But usually with a bit of care they can be worked around, although the approach tends to be a little "brute force"ish.

    Mark

      sorry did you say migrate? If your using javascript html/css you got to make sure it works in all browsers. Just remember if you dont get it to work in FireFox thats a huge chunk of visitors your going to loose especially with FireFox tearing through IE's marketshare like a raging bull

      The web and migrating there is no such thing your either cross browser capable or not

        Originally posted by planetsim
        The web and migrating there is no such thing your either cross browser capable or not

        Well - I'd half go along with that: one can migrate from IE-specific code to cross-browser compliant code (or any $vendor-specific code to cross-browser - it's possible to write stuff that only works in Mozilla - even in HTML and CSS)).

        But once you're cbc, it would be a distinctly unpleasant feeling to have to move back to running only on a particular product.

          yeah im trying to make it work on both..

          btw i tried the javascript debugger many times and all it would say is that my variables were undefined.. or didnt exist.. that didnt get me too far 🙁 I tried using some frames syntax i found off of i think w3.org and it didnt work either.. I dont know if what im doing is hard in mozilla or what? Im having no luck with getElementById('blah');

          But ive figured everything else out on my own so oh well ill figure it out eventually.. it was just giving me a headache as i tried things for hours that they said were mozilla compliant and i just couldnt get them to work, which is why i started asking for help.

            Try here for a good forum dedicated to javascript. That would be a better place for you to seek javascript help then in the php forums.

              thanks 🙂

              and btw, i DO like firefox.. it's nice and clean.. i was just basically trying to make a joke and i guess firefox is a touchy subject haha.

              Ive just never had a problem with XP or IE is all im trying to say. I know lots of people DO have security issues though.

                Originally posted by Jinks
                yeah im trying to make it work on both...

                This could be part of your problem. It's not a matter of "IE only" versus "IE and Mozilla"; it's "IE only" versus "IE and any sufficiently modern browser". That includes Mozilla/Firefox/Netscape7/Warpzilla/generally anything using the Gecko rending engine; Opera, and no doubt a small horde of others whose names don't occur to me at this instant. Oh, yes: Safari, Konquerer, ....

                Im having no luck with getElementById('blah');

                The most trouble I've ever had with it has been remembering to capitalise the 'B' and not the 'g'. Give the element you want to refer to an id= attribute and you're away.

                But yes, the W3C is a good place for reference material. The DOM in particular; the Javascript language itself isn't maintained by them, however. A place to look at that might be here (ECMA themselves aren't too hot at the job in my opinion); though for the supra-DOM stuff like "window", "application", (everything above "document" - which the DOM doesn't cover, by definition) you could look at this.

                  what have i started, doh!

                  for my needs and wants, I like to have IE fixed with, I had some issues with IE that are just plane differnt. I had issues with a Simple BR tag, It worked with everything but ie.

                  As a web designer, you have to like all of them because its not our choice. its the person on the other ends choice what browser they want to use.

                  I did have a issue with firefox and pdf. (lockup someties on exit)

                  anyhow i dont want to turn this in to a browser war. so please no wars, have we not seen too many wars? 🙂 hehe thanks,

                  i did not expect this much action on this post. just wanted to alert people of software was out.

                  Besides having to patch my IE every other week with windwos upgrade, hey its normal right? 🙂

                  Anyone have this happen, webpages sometimes load in text (source format) insted of the rendered html view.. i would have to click Reload. (only happens one time per page not all the time, at random maybe 1 page out of 30)

                  have fun,

                    well ive got it ALL figured out now 😃 I just had my syntax a little bit off every time i was testing on mozilla.. Thanks for all the help weedpacket and everyone else giving links.

                    It took me a while to figure some things out because the way netscape does soem things is so much different..

                    anywhooo.. it now works on BOTH IE and mozilla.. if anyone cares i will post the code of the working script.. hmm

                    PS.. zapa. sometimes i find a page wont load properly if my internet connection is getting ltos of packet loss .. sometimes it doesnt pick up the style sheets properly and as a result displays the page as plain text 😃

                      IE will not die until windows dies. The reason, if you really want to hear it, is simplicity. The average person donesn't give a crap about why IE sucks. What the average person cares about is I can surf the web. So as long as they can use IE on their PC right out of the box they will.

                        Originally posted by drawmack
                        IE will not die until windows dies. The reason, if you really want to hear it, is simplicity. The average person donesn't give a crap about why IE sucks. What the average person cares about is I can surf the web. So as long as they can use IE on their PC right out of the box they will.

                        Nooooooooooooooooooooooo...is all I have to say.

                        :p

                          Originally posted by drawmack
                          The reason, if you really want to hear it, is simplicity.

                          Don't you mean "apathy"?

                            Originally posted by Weedpacket
                            Don't you mean "apathy"?

                            Sure but the apathy comes from the simplicity. If there were no browser bundeled with windows then they would have to care enough to get and install one.

                              Write a Reply...