Home

Results 1 to 4 of 4

Thread: iPrint client chrome plugin uses deprecated npapi protocol

Hybrid View

  1. #1

    iPrint client chrome plugin uses deprecated npapi protocol

    Hi,

    I was really happy to see Chrome support for the iprint plugin. But it's using the npapi which is deprecated and doesn't work in chrome version 42 and higher.

    I can't understand why Novell uses a deprecated api to make a plugin when google accounced in sept 2013 that it would drop npapi.

    Stefan.

  2. #2
    Mysterious NNTP User

    Re: iPrint client chrome plugin uses deprecated npapi protocol

    On 08/10/2015 02:26 PM, spcox wrote:
    >
    > Hi,
    >
    > I was really happy to see Chrome support for the iprint plugin. But it's
    > using the npapi which is deprecated and doesn't work in chrome version
    > 42 and higher.
    >
    > I can't understand why Novell uses a deprecated api to make a plugin
    > when google accounced in sept 2013 that it would drop npapi.
    >
    > Stefan.
    >
    >

    tid 7016444

  3. #3

    Re: iPrint client chrome plugin uses deprecated npapi protoc

    I know,

    But have a look at this blogpost from 2013!
    http://blog.chromium.org/2013/09/say...end-npapi.html

    And then still choose for npapi to create a plugin.....

  4. #4
    Mysterious NNTP User

    Re: iPrint client chrome plugin uses deprecated npapi protocol

    On 08/10/2015 03:26 PM, spcox wrote:
    >
    > I know,
    >
    > But have a look at this blogpost from 2013!
    > http://blog.chromium.org/2013/09/say...end-npapi.html
    >
    > And then still choose for npapi to create a plugin.....
    >
    >


    on the tid there is a link to provide feedback. Use it and provide
    feedback to novel engineering.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •