Repository navigation
spec(AST-094): touch presentations feel native by default #8378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6fd240b
spec(AST-094): touch presentations feel native by default
cixzhang ffb5a0b
spec(AST-094): the records it amends point to it; review fixes
cixzhang 90f626b
spec(AST-094): rulings on touch ownership and roles; review fixes
cixzhang 0024510
spec(AST-094): verification rows follow FR19 and FR26; useMenuPress r…
cixzhang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -72,10 +72,12 @@ requirements. Assistive-technology evidence remains separately owned. | |
| public [Browser Support guide](../../../packages/cli/assets/docs/browser-support.doc.mjs) | ||
| and record their source and refresh date. TypeScript targets, build targets, and | ||
| feature tables are not support evidence. | ||
| - **FR3 — Two explicit browser support rows are always included.** Independently | ||
| - **FR3 — Explicit browser support rows are always included.** Independently | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. FR3 now names three explicit rows, but DEC-1 ("plus two official browser rows") and DEC-2 ("DEC-1's two named browser rows") still count two. Name the Android row there, or refer to FR3's named rows. |
||
| of the generated Baseline coverage, Astryx explicitly supports: | ||
| - the latest stable Chrome release on desktop; and | ||
| - Safari on the latest stable iOS release. | ||
| - the latest stable Chrome release on desktop; | ||
| - Safari on the latest stable iOS release; and | ||
| - for touch presentations, Chrome on the latest stable Android release | ||
| (`spec:AST-094`). | ||
|
|
||
| “Latest” means the current stable release identified and refreshed from | ||
| authoritative browser release data, not a handwritten version. Other browsers | ||
|
|
||
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FR11 says when a control highlights, not what a selected item paints, so under a finger nothing says whether a held, selected SegmentedControl item keeps its raised surface, adds the pressed overlay, or gives it up. State it here or in FR11.