2021-02-04

• Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=89f8353c8bdbc0db5a4aba743d4c91e96da383b5
• Downloads (from Try): Windows 2012 x64 opt | OS X Cross Compiled opt | Linux x64 opt

2021-01-13

• Try: https://treeherder.mozilla.org/jobs?repo=try&revision=556cafb5f97aa7eb9f35ec957c1517013695c511
• Downloads (from Try): Windows 2012 x64 opt | OS X Cross Compiled opt | Linux x64 opt

2020-11-30

• Try: https://treeherder.mozilla.org/jobs?repo=try&revision=3526ce6e2696761987bfbfa5bf1b8741ee082852
• Downloads (from Try): Windows 2012 x64 opt | OS X Cross Compiled opt | Linux x64 opt
• Notes: Run with ./firefox --jsconsole

What's supported?

• Getting monetization details from the first valid <link> element at any time. That is, if you add or remove or modify the link elements, the monetization info is updated. This way, dynamic monetization tags support revenue sharing and single-page applications (SPA) use cases.
• Monetizing only the currently visible tab in the browser (no background tabs).
• Fetching the payment info with proper HTTP headers, while respecting CORS policy and cache-control behavior, as defined by the SPSP protocol.
• To preserve user's privacy, no referrer information (i.e., the URL of current website) or cookies are sent to the monetization receiver (e.g. Uphold).
• Logging error messages and other information to the browser console.

What's not supported?

Implementation only handles the fetching and processing of the monetization endpoint (payment pointer), and not the actual monetization.

Read my first report for details.