Announcement

Collapse
No announcement yet.

Google Puts Chrome NPAPI Support On Final Countdown

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Google Puts Chrome NPAPI Support On Final Countdown

    Phoronix: Google Puts Chrome NPAPI Support On Final Countdown

    Google is moving towards the final steps in eliminating Netscape Plugin Application Programming Interface (NPAPI) plug-in support from the Chrome/Chromium web browser...

    http://www.phoronix.com/vr.php?view=MTg0Njc

  • #2
    long time out for linux users

    since version 35 i think, if we want use java web plugin we need firefox or other no news for linux users here

    Comment


    • #3
      Exactly, d-day on Netscape interface was ages ago for Linux.

      Java is still needed and hence why I boot ff.
      Then there is the media plugins..

      I wonder if Java will convert over and whether there is any drive...

      Sure javascript and html5 would be great but sites are taking their time

      Comment


      • #4
        Yep, version 35 released last May was it for Linux.
        Last edited by Scimmia; 11-24-2014, 03:10 PM.

        Comment


        • #5
          I had no idea NPAPI was still used. Seeing as how I don't use any NPAPI plugins and haven't for probably 10 years, I personally won't miss it.

          Comment


          • #6
            Finally NPAPI is coming to an end and may all the damned browser plugins die with it!

            I wonder what are Mozilla's plans now that their h264 implementation uses NPAPI! Is this going to delay their plan on also eliminating NPAPI?

            Comment


            • #7
              Originally posted by jntesteves View Post
              Finally NPAPI is coming to an end and may all the damned browser plugins die with it!

              I wonder what are Mozilla's plans now that their h264 implementation uses NPAPI! Is this going to delay their plan on also eliminating NPAPI?
              1. you realize the only reason Chrome is disabling it is because they want to push their proprietary PPAPI architecture, right? Browser plugins aren't going to die, they're going to become even worse.
              2. Mozilla currently has no plans of killing off NPAPI, since PPAPI really isn't a viable option for any non-chromium-based browser (for various reasons).

              Comment


              • #8
                Originally posted by Daktyl198 View Post
                1. you realize the only reason Chrome is disabling it is because they want to push their proprietary PPAPI architecture, right?
                1) Google did a smarter, trickier thing. PPAPI is designed to be such a product that it's perceived as "open" but in reality you can't create an open (cross-browser) plugin because PPAPI has too many poorly documented or undocumented features or which are tailored to Chrome's needs which is a no-go for non-blink, non-webkit browsers. In this sense it's not Mozilla the asshole, it's Google.

                2) Despite the fact that non-blink browsers can't realistically adopt PPAPI, it doesn't change the fact that (in Firefox) we still need a more modern plugin stack than the old NPAPI.

                Comment


                • #9
                  Originally posted by mark45 View Post
                  1) Google did a smarter, trickier thing. PPAPI is designed to be such a product that it's perceived as "open" but in reality you can't create an open (cross-browser) plugin because PPAPI has too many poorly documented or undocumented features or which are tailored to Chrome's needs which is a no-go for non-blink, non-webkit browsers. In this sense it's not Mozilla the asshole, it's Google.

                  2) Despite the fact that non-blink browsers can't realistically adopt PPAPI, it doesn't change the fact that (in Firefox) we still need a more modern plugin stack than the old NPAPI.
                  Mozilla should reach out for suggestions for a new plugin implementation that's open yet more secure than the old NPAPI structure.

                  Comment


                  • #10
                    Originally posted by mark45 View Post
                    1) Google did a smarter, trickier thing. PPAPI is designed to be such a product that it's perceived as "open" but in reality you can't create an open (cross-browser) plugin because PPAPI has too many poorly documented or undocumented features or which are tailored to Chrome's needs which is a no-go for non-blink, non-webkit browsers. In this sense it's not Mozilla the asshole, it's Google.
                    That sounds just like Office Open XML.

                    Comment

                    Working...
                    X