IcedTea-Web and chrome/chromium?

[gitne at gmx.de]

On Thursday, November 27th 2014 at 02:11:08 PM Jiri Vanek wrote:
>> On 11/27/2014 01:50 PM, Guillaume Alaux wrote:
>> Hi all,
>>
>> So I understand chrome/chromium moved away from NPAPI last year [0]
>> but I still see a lot of references to chrome/chromium in IcedTea-Web
>> sources (the ./configure for one takes these `--with-chrome` and
>> `--with-chromium` params) and also on the wiki page.
>>
>> So just to be sure: IcedTea-Web has nothing to do with **recent**
>> versions of chrome/chromium right?
>>
> Yes you are right, ITW do not work on chromes now, because of missing npapi. The challenge to write
> ppapi (or whether to do so at all) plugin is still open.

I may get to do this, since I would like to implement IcedTea-Web as an ActiveX control for the Internet Explorer.
So, after that, PPAPI might be next, but probably primarily for Windows only, although PPAPI is supposed to be designed platform independent. Nevertheless, most testing will probably happen on Windows first.
I cannot give you any time estimate when this going to happen (if only I could get hands on my new machine...).

Just on a side-note: Deprecating NPAPI in favor of any new API will not really solve any of the problems users and mostly administrators are currently plauged with. The core problem is, as usual, hastly written and buggy plug-ins, not the API. So, it is a stupid thing to do. Simply introducing a new API and believing that now things are going to be much better is just stupid and naive. I am not saying NPAPI is perfect, and there is sure room for improvement, but is also not that bad. 
> 
> The lines about chromium are for testsuite only. I have still some systems with old chrome/chromium,
> and from time to time I try those.
> 
> J
>> 
>> [0] http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
>> 
> 
> J.