Skip to content
This repository was archived by the owner on Nov 7, 2024. It is now read-only.

Describe navigation as a capability, not a goal. - #33

Open
jyasskin wants to merge 2 commits into
w3cping:mainfrom
jyasskin:navigation-is-a-capability
Open

Describe navigation as a capability, not a goal.#33
jyasskin wants to merge 2 commits into
w3cping:mainfrom
jyasskin:navigation-is-a-capability

Conversation

@jyasskin

@jyasskin jyasskin commented Jun 4, 2020

Copy link
Copy Markdown
Member

This reduces the number of goal columns at the cost of increasing the number
and complexity of rows in the table. I hope it makes it easier to see what
abilities an attacker gains when they're willing to show the user a navigation.

This depends on #32 to make sure the resulting columns all match up.


Preview | Diff

@hober hober left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like it redundantly contains the changes in #30 and #32.

This reduces the number of goal columns at the cost of increasing the number
and complexity of rows in the table. I hope it makes it easier to see what
abilities an attacker gains when they're willing to show the user a navigation.
@jyasskin
jyasskin force-pushed the navigation-is-a-capability branch from b2e32c4 to 7e61630 Compare August 6, 2020 18:19
@jyasskin

jyasskin commented Aug 6, 2020

Copy link
Copy Markdown
Member Author

Yep, this change is the third in a stack that all collide with eachother. You can review just one using a dropdown in the "Files changed" pane:

"Changes from 1 commit" dropdown

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants