More Flash technical discussion on what you can do:
http://www.rewindlife.com/archives/000086.cfm

----- Original Message ----- 
From: "JesterXL" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list" <[email protected]>
Sent: Saturday, December 03, 2005 2:19 PM
Subject: Re: [Flashcoders] Microsoft tweaks browser to avoid liability


Digg.com's link has a better write up of the interaction changes:
http://www.eweek.com/article2/0,1895,1895907,00.asp

However, the quote:
"...Instead of non-stop dialog boxes, the page will load normally now and
won't be as disruptive. It will only require a click to activate [the
control] if the user wants to interact with it,..."

Doesn't explain if Flash movie's need to have the user click on them before
they can play, like FlashBlock.

----- Original Message ----- 
From: "JesterXL" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list" <[email protected]>
Sent: Saturday, December 03, 2005 1:53 PM
Subject: Re: [Flashcoders] Microsoft tweaks browser to avoid liability


Watch this space:
http://www.macromedia.com/devnet/activecontent/

JD reported on it here:
http://weblogs.macromedia.com/jd/archives/2005/12/eolas_re-re-re-.cfm

Jeffrey Zeldman has a fallout article from 2 years ago about it.  This was
the time when the FUD was reaching its apex:
"Eolas: first fallout"
http://www.zeldman.com/daily/0903c.shtml

If you followed the link, through the plethora of discussions, it all falls
down to controls don't work until you "click" on them.  They still respond
to JavaScript on the page, such as:

myFlashMovie.focus();

To allow them to be immediately available, you simply use JavaScript to
dynamically write the code, such as FlashObject.js.

While technically this is a minute change, it has far reaching implications
on existing content where the simple suggestion above doesn't work as
intended, or at all.  Even worse is this is Microsoft taking the
initiaitive, to pretty much protect themselves now, so if things do NOT go
their way, they are already technical compliant.  They feel that their
changes do 2 things, first, quell the uneasiness that this lawsuit has
caused over the past 2 years, and second, protects the for the future.

They are wrong on both accounts.  The first, revives ALL the email threads,
forum posts, and technical articles put out by large companies such as Real,
Apple, Macromedia, etc. on how to ensure your existing and new content works
with the changes.  It does little to quell anything, and rather makes all of
this resurface.

Secondly, there is no guarentee that EOLAS won't sue on their current
implementation.

I couldn't find the link, but basically I think ICANN pleaded with the US
government that if they didn't take action on this patent case, it would
negatively affect the way the internet works.  That got their attention, and
slowed the case to a crawl.

Anyway, Jeffrey's final comments eximplfy the FUD:
"...Few of Happy Cog's commercial sites have used embedded media. We are
reluctant to wake old clients from their dream that all is well, and
convince them to let us recode old sites, only to discover in another few
weeks that Eolas is suing again."


----- Original Message ----- 
From: "Jason Cunliffe" <[EMAIL PROTECTED]>
To: "Flashcoders Mailing List" <[email protected]>
Sent: Saturday, December 03, 2005 10:59 AM
Subject: [Flashcoders] Microsoft tweaks browser to avoid liability


Can anyone clarify please what changes will now need to be made by Flash
authors ?

CNET article yesterday:

-- Microsoft tweaks browser to avoid liability --
Microsoft is changing the way its Web browser handles certain controls in an
effort to shield itself from liability in an ongoing patent spat with a
start-up backed by the University of California.

>> see the full text article here:
http://news.com.com/Microsoft+tweaks+browser+to+avoid+liability/2100-1012_3-5980658.html

thanks


_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders 

_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to