In T179529: [Spike] Can we detect browsers where the window.print function simply doesn't work? we saw that on Android, the print to PDF button only works for Chrome browsers. Thus, we would like to give the functionality to all other browsers by rendering the PDFs via headless Chromium. We would like to get an estimate of the amount of traffic these renders will have.
- Test that the Print instrumentation works as expected for Chrome mobile on Android, both for the standard print path ("Share" --> "Print") and for the custom PDF download button deployed on November 15 (T179914). See e.g. the testing method described at T179914#3767547 and the discussion at T181297 .
--> done in T181297#3920633 ff. (at least for the download button)
- Review print button usage on Chrome mobile using the Print instrumentation to determine average number of prints per pageview per minute/hour/day/month.
- Use the above data to create rough estimates for usage for the following browsers based on their pageviews for the same period:
- Firefox mobile
- Opera mobile
- Opera mini
- UC Browser
- Daily pageviews, at least, are available in Pivot.
- We would begin looking at usage after T179914: Deploy print to PDF button for Chrome on Android is complete (the button is deployed to Chrome)