Chrome’s built-in PDF viewer relies on a native plugin that uses the Pepper Plugin API (PPAPI). Pepper is slated to be removed as part of the (P)NaCl deprecation and the end of support for Flash. We plan to migrate the PDF viewer plugin from a separate Pepper process into an ordinary renderer process, and to migrate all Pepper API calls to the renderer-native equivalents. This will unblock Pepper removal, and simplify the PDF viewer.
Mac, Windows, Linux, Chrome OS (the built-in PDF viewer only exists on desktop platforms)
Project lead: km...@chromium.org
Team TL: the...@chromium.org
Plugin handling
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CACwGi-4ZK7-4f2Ke%2B8puxu8PVGe64rTddwVt2H%3DCDP_ODHfqvQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CABiGVV8x%2BzFsPC24PbwMWV6hiVhNQ7Mu_i49cao8RpNzT4vGAQ%40mail.gmail.com.
Behaving more like a web renderer would seem to open the doors to lots of potential improvements, like better compositor integration.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CACuR13c%2BYNuuzk%2By_UkUXgv-oyVHvuv-dyy45CkyCenB4jxpWw%40mail.gmail.com.