Changes are almost entirely related to forced transition to another API version for Chrome extensions. Minor fixes:
-
Earlier zero-width space characters U+200B were added after timestamps. You may want to remove them from your notes, use search and replace for
:LAST_MODIFIED: [2021-09-18 Tue 01:23]<200b> 09/18/2021 01:23:46 -
Only first
<script>element with JSON-LD metadata was taken into account. -
In Chrome tab group may be captured in addition to highlighted tabs. Use menu for the extension in the browser toolbar (context menu if the icon is pinned).
As to Manifest V3 API, it required significant amount of work. New bugs may appear due to more complex initialization. I have no idea if smaller RAM footprint of browser is noticeable. Despite some permissions are optional now, I do not think the add-on has become more safe. Multiple tabs and cross-origin frames scenarios still require most dangerous <all_urls>. From my point of view, security model for browser extensions is still far from being consistent. Firefox version uses Manifest V2 API as in earlier releases due to bugs in mv3 implementation. I agree with the opinion that primary goal of forcing Manifest V3 API is to restrict ad blockers, not user safety.