Did you read the first post? :p It stands for Internet Explorer.
"Explosion" http://forums.pcpitstop.com/style_em...cons/rofl2.gif
Printable View
Did you read the first post? :p It stands for Internet Explorer.
"Explosion" http://forums.pcpitstop.com/style_em...cons/rofl2.gif
It did not say what IE stands for? ;) It says "...Microsoft will be releasing Internet Explorer 8 to render content..." So IE is Internet Explorer...? Now I remember, it must be years ago when I had Mac OS 8 or 9. I don't like companies, which neglect certain Operating systems completely.
And just for the record: the most problems in Flash occur with Ish*t Expl. That is where I get most problem questions.
That's where the 1+1=2 logic was supposed to kick in. Use this in the future. :p
Code:var txt1:String = ("Internet Explorer 8").toUpperCase();
var txt2:String = ("IE 8").toUpperCase();
if(txt1.indexOf('8') && txt2.indexOf('8'))
{ trace("These two seemingly unrelated items share a revision number.");
// since txt2 is a constant, we can determine ourselves that it isn't a
// word in the English language, so we assume it's an acronym. Let's see if it
// matches anything in txt1.
var matches:Number=0, begin:Number=0, i:Number=0;
var compare:String;
while(txt2.charCodeAt(i) != 32)
{ if(txt1.charCodeAt(begin) == txt2.charCodeAt(i))
{ matches++;
}
begin = txt1.indexOf(" ",begin) + 1;
i++;
}
if(matches==i) trace(txt2 + " is an acronym for " + txt1);
}
Are you payed by Bill Gates?
Bill retired. I answer to Ballmer now. :D
You have more problems with flash in a specific browser?
Interesting...
Most of the browser questions regarding problems in the forum are about IE. One reason is that IE is not as precise as other browsers and also there is a caching problem and when you load images by a loop they often do not all appear. IE always costs extra time.
This argument is pointless. The fact of the matter is that MS painted itself into a corner on this one.
They dominated market share, then let the browser stagnate, all the while passively promoting the use/abuse of its quirks by not fixing them at regular intervals.
IE8 is going to be painful for a lot of people, but necessary. Some older smaller sites are going to break, all of a sudden DocType is going to become important. Transition sucks, but if it's done right it's worth trudging through the BS.
What I particularly dislike is MS basically introducing their own DocType spec with these meta tags. It's the exact opposite of what they should be doing. Instead of promoting more IE specific workarounds and quirks, they need to get in line.
Guess what else? Dollars to doughnuts says Silverlight is bundled in.
So when do we get HTML5 and XForms support?
Just some interesting uses of our new friend the .pdf.Quote:
Originally Posted by FlashLackey