removing OJI, LiveConnect, and the XPCOM plugin API in Gecko 1.9.2 - mozilla.dev.planning

Message from discussion removing OJI, LiveConnect, and the XPCOM plugin API in Gecko 1.9.2

josh...@gmail.com

More options Mar 22, 9:31 pm

Newsgroups: mozilla.dev.planning

From: josh...@gmail.com

Date: Sun, 22 Mar 2009 18:31:00 -0700 (PDT)

Subject: Re: removing OJI, LiveConnect, and the XPCOM plugin API in Gecko 1.9.2

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

On Mar 22, 5:18 pm, Boris Zbarsky <bzbar...@mit.edu> wrote:

> josh...@gmail.com wrote:
> > To put this change in perspective in terms of a timeline, the earliest
> > a browser with those changes would ship would be approximately Q2
> > 2010.

> Is that seriously how late the release after 1.9.1 is planned for?
> That's rather sad-making. I was hoping we'd do a Gecko release before
> that. :( Was there a discussion I missed somewhere?

This is an estimate of mine, I haven't heard any formal plans. Planned
is < actual in almost every case anyway, and Q2 2010 is less than 1
year after 1.9.1. I'd be extremely surprised if we saw a 1.9.2 release
before March of 2010.

> > The argument against committing now is that we'll go for a period of
> > time on the trunk without a Java plugin on Mac OS X and without Real
> > player on all platforms. However, we are not losing regression
> > coverage because both plugins are being replaced entirely and users
> > that actually need those capabilities can use Firefox 3.5.

> We might be using trunk testing coverage in general, though, if people
> can't use it because sites they rely on don't work without Java.... Do
> we have any data on this?

I think the number of Mac OS X trunk nightly users that rely on Java
so much that they can't occasionally use Firefox 3.5 for a bit is very
small. I'm not worried about their impact on overall nightly testing
coverage. I have no idea where we'd get data on that.

Reply to author Forward