Currently, the Chromium extension picks up all tags regardless of their location in the document (head or body) unlike the Chromium prototype, which scoped monetization elements to the document , the WM spec (https://webmonetization.org/specification/#link-type-monetization) doesn't seem address that explicitly.
Discussion points:
The HTML spec allows elements in the body ("body ok"), so there is no restriction on their placement.
The extension currently treats all tags equally, with a to-do for handling those within media elements.
One theoretical use case for in the body is dynamic activation/deactivation (e.g., using IntersectionObserver for monetization in a feed of posts from different authors), but this is not implemented or spec'ed anywhere.
Action:
Clarify documentation whether we intend to support elements outside the , and if so, under what conditions.
Ref: #17 (comment)
Currently, the Chromium extension picks up all tags regardless of their location in the document (head or body) unlike the Chromium prototype, which scoped monetization elements to the document , the WM spec (https://webmonetization.org/specification/#link-type-monetization) doesn't seem address that explicitly.
Discussion points:
The HTML spec allows elements in the body ("body ok"), so there is no restriction on their placement.
The extension currently treats all tags equally, with a to-do for handling those within media elements.
One theoretical use case for in the body is dynamic activation/deactivation (e.g., using IntersectionObserver for monetization in a feed of posts from different authors), but this is not implemented or spec'ed anywhere.
Action:
Clarify documentation whether we intend to support elements outside the , and if so, under what conditions.
Ref: #17 (comment)