On Fri, Feb 11, 2011 at 08:00:23AM -0700, Rob Savoye wrote: > On 02/11/11 07:33, strk wrote: > > > Both me, Gabriele and Benjamin can easily reproduce the crashes > > of the plugin, on both chromium and firefox. > > If you were paying attention, everyone is getting the plugin crash, > myself included.
The tracker must be underused. Both bugs are missing follow ups by "everyone". It would help to get a notice on the record about which browsers (and versions) show that behavior and which one don't (pere seems to be saying he doesn't get it ?) > I assume we missed this as most just do "make install" > and not "make install install-plugin". But yes, this is a definite blocker. Glad we agree on the severity :) > I believe it's a bug in the patch that added support for executing the > JavaScript side of ExternalInterface. Ben reported a revert of that patch did not fix it. > > I'd rather drop the EI support and get a stable browsing experience > > if the author isn't willing to find and fix the bug. > > Author of which code ? Dropping all of EI is downright silly, and not > exactly a trivial change. Author of the ExternalInterface code. Yes, I've noticed EI got intermixed with how we do getURL and fscommand. That might have been an unfortunate decision indeed. > Either way, I gave up getting the release out for the Fedora and > Ubuntu code freezes. They'll have to grab it as a future update. While I > do appreciate all this last minute testing and bug fixing, it really > needed to have happened several weeks ago... #31766 was submitted on 03 Dec 2010 as Important #32044 was submitted on 04 Jan 2011. That's what I meant by "going through the bug tracker" --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
