Remove references to the Declarative Link Capturing proposal #30
Conversation
This file contains 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
alancutter
added
the
scope-extensions
kenchris
reviewed
May 2, 2022
|
Looks like this needs a rebase... |
|
I'll take over. (Discussed privately with @alancutter ) |
The new section is essentially a rewrite of this.
alancutter
commented
May 31, 2024
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.
Declarative Link Capturing is no longer being pursued in favour of launch handling and unspec'd browser behaviours. This updates the scope extensions explainer to no longer tie itself to DLC and instead reference launch handling where relevant.