docs: refresh userscript compatibility notes#450
Merged
Manuito83 merged 1 commit intoMay 23, 2026
Conversation
Owner
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @Manuito83, this is the docs-only follow-up from the older userscript DX work in #289.
While checking what is still left there, I noticed the GM compatibility doc is a little stale: it still marks some behavior as TODO even though the current app already parses grants/requires, has improved @match handling, includes baseline GM handlers, and replaces ###PDA-APIKEY### at injection time.
This PR only updates the documentation to better reflect the current state. It does not change app behavior.
I kept the remaining TODOs explicit, especially @require loading, @include/@exclude, and a possible future compatibility matrix. Please let me know if any wording should be more conservative.