Update well-known destinations explainer in accordance with TPAC 2024 #279
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
| . . . | ||
| <head> | ||
| . . . | ||
| <link rel="accessibility-statement" href="/accessibility-statement"> |
There was a problem hiding this comment.
Can we have following:
- List of possible values for rel attribute? I think UA will look for link tag with some pre-defined rel values...
- How this list can be enhanced, as websites may have very different structures?
| <head> | ||
| . . . | ||
| <link rel="accessibility-statement" href="/accessibility-statement"> | ||
| <link rel="help" href="/support"> |
There was a problem hiding this comment.
The User Agent will show image and title for navigation. Will it coming from title and icon attributes? Will title be in user locale?
If yes, can we enhance explainer to capture these?
|
|
||
| The UA will know if this link points to the root of the well-known destination (e.g. the "Help" landing page, vs "Help on logging in") becuase it knows the URL of the root of the well-known destination, via the discovery process above. | ||
| ```html | ||
| <p>For more details, consult the <a href="/help/signing-in" rel="help">help section on signing in to your account</a>.</p> |
There was a problem hiding this comment.
- Will UA parse all the anchor tags ?
- If yes, how will it know that is anchor is relevant for Well-known-destination?
- Does this also mean that UA will show union of result from anchor and link tags?
|
|
||
| This approach builds on: | ||
| * Highlighting the specific relevant part of the page. |
There was a problem hiding this comment.
Can we detail out how a browser extension can achieve it?
| > This was the TF's favoured approach pre-TPAC 2024. Keeping this here for now to help write the revised, simpler, one, and to possibly be used to offer an idea of how the approach _may_ be made more efficient in future if there is demand. | ||
|
|
||
| > [!NOTE] | ||
| > This approach originally had 'defining a site' immediately after the first, namespace, section. This has been moved to reflect the heading structure above. |
|
|
||
| * A single Well-known URI from which the linkset would be served; and | ||
| ## Previous iteration: Linksets |
There was a problem hiding this comment.
This section doesn't capture, why we are not using this approach?
|
|
||
| We first explored using [Well-known URIs](https://datatracker.ietf.org/doc/html/rfc8615), which provide a number of useful features. However, there were some important limitations: | ||
|
|
||
| * Well-known URIs are linked to an _origin_ which means it's not possible to demarcate sub-sites. |
There was a problem hiding this comment.
We can have different well-known URLs for sub-sites. I think the issue is with sub-pages.
| @@ -388,6 +392,9 @@ It does not seem like a good fit to try to extend the format of sitemaps to acco | |||
|
|
|||
| ### Using `rel` attribute values alone | |||
|
|
|||
| > [!WARNING] | |||
There was a problem hiding this comment.
This section looks confusing. We can discuss and possibly re-phrase it.
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.
Preview: https://github.com/w3c/adapt/blob/explainers-post-tpac-2024/explainers/well-known-destinations.md