← Back to team overview

lightspark-users team mailing list archive

Fwd: Re: Issue 108962 in chromium: Wrongly warns about "Flash plugin" being out-of-date, when it's lightspark, not Adobe's

 

Just forwarding to lightspark-users@ instead of sparkers@ which doesn't seem 
used…

See attached mail.

-- 
OdyX
--- Begin Message ---
Le mardi, 3 janvier 2012 12.00:40, chromium@xxxxxxxxxxxxxx a écrit :
> Updates:
> 	Cc: stuartmorgan@xxxxxxxxxxxx
> 
> Comment #2 on issue 108962 by bauerb@xxxxxxxxxxxx: Wrongly warns
> about "Flash plugin" being out-of-date, when it's lightspark, not Adobe's
> http://code.google.com/p/chromium/issues/detail?id=108962
> 
> Hm. The problem is that Lightspark calls itself "Shockwave Flash" in the
> plug-in description, so we can't distinguish it from Adobe Flash from the
> description alone.

Sparkers: What is the reason behind lightspark mimicking the "Shockwave Flash" 
identifier ? What would break if Lightspark would announce itself "Lightspark 
Flash player" instead? Then it would "just" be a matter of filing bugs against 
the mis-behaving browsers, right?

> We could either extend the plug-in matching logic to also take MIME types
> into account, or as a simpler but hackier solution recognize the 10.2.530
> version (Adobe Flash is at 10.3.x, where x << 530, so there probably won't
> be a version in that range).

Note: the "530" number is created from the 0.5.3 version number of Lightspark, 
so basing any detection on that is most probably not future-proof.

-- 
OdyX (N.B. I'm didier.raboud@xxxxxxxxx too)

--- End Message ---

Attachment: signature.asc
Description: This is a digitally signed message part.


Follow ups