Comments on: EOLAS & IE Quick Fix Doesn’t Work

By: JesterXL

JesterXL — Wed, 15 Oct 2003 17:07:50 +0000

That’s what confused me. It mean external to the page. I interpretted it originally as external to the domain or “site”, but if it’s not on the page, it’s external, so I think what you say is accurate… I guess, I’m still trying to figure it all out.

By: nick

nick — Wed, 15 Oct 2003 17:01:35 +0000

Isn’t the codebase “External data” ?

By: JesterXL

JesterXL — Thu, 09 Oct 2003 21:43:33 +0000

Mario, I was definately figuring towards the end that it was page relative, not domain relative. …bleh.

Simon, thanks for the clarification, it’s nice to have it succinct since there is so much info out there. Trust me, I know there are a lot more, I’m just covering what is my job related function first, can you blame me for being selfish, hehe?

JD, sorry bro, I know. I’ve used MT’s default CSS which on it’s own blows, and I’ve ravaged it being comprehension (my first use of CSS). When contract is done, I’m redoing my site from scratch which will hopefully solve some of the Safari & Mac display issues as well. Sorry about the text, try going to the trackback which should have the article alone.

Not really a concern, more of a gripe: I’m forced to use JavaScript because the first solution provided didn’t work. However, now that I understand the first solution is page relative, not domain relative, the JavaScript one is ok (I’m not happy about it, but I’ll live); what my concern is relates to this being all a proposal and may not be the way things work. If it is the final say, cool, I’ll just External JS my life away.

By: John Dowdell

John Dowdell — Thu, 09 Oct 2003 21:32:20 +0000

Hi Jesse… this blog page has problems rendering in my Mozilla 1.4… I highlighted the text to read it and scanned through a few screens… seems like the core is “I’m having varied troubles with MS’s ’embedded data’ solution”, which I’d expect, considering that other browsers can’t read it and you’d still need the EMBED for other browsers which would throw up the IE/Win permissions dialog. The material on the Macromedia site (with the “write it from external .JS” approach) is less MC-centric.

I’m not sure I caught the correct core concern there though…?

jd/mm

By: simon

simon — Thu, 09 Oct 2003 21:28:55 +0000

The noexternaldata tag only works if the content of the object tags does not contain data that is external to the “page”, not the “domain”. Since Flash is always referencing an separate SWF this doesn’t work and the javascript trick is required.

The way I read it this attribute only works when referencing objects that Microsoft has built into the browser. I’m not familiar with any of the, but I perhaps IE application developers or intranet programmers could give some examples.

Remember, this change affects way more than just Flash content.