Skip to content
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

editorial: Reword requirements in "Security and privacy considerations" #114

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

rakuco
Copy link
Member

@rakuco rakuco commented Oct 30, 2023

Use more modern spec terminology in the list of requirements for firing
device orientation and motion events:

  • Use navigables and concepts defined for navigables when dealing with
    windows and documents.
  • Stop referring to the PAGE-VISIBILITY spec, as it was merged into HTML a
    few years ago. Use a document's visibility state instead.
  • Use more precise terms when laying out the same-origin requirements
    between the top-level traversable and its child navigables. The new
    paragraph is a mouthful, but also more precise.
  • Instead of referring to the SECURE-CONTEXTS spec, use HTML's definition of
    "secure context".

This change should not cause any behavioral or user-detectable changes.


Preview | Diff

Use more modern spec terminology in the list of requirements for firing
device orientation and motion events:

- Use navigables and concepts defined for navigables when dealing with
  windows and documents.
- Stop referring to the PAGE-VISIBILITY spec, as it was merged into HTML a
  few years ago. Use a document's visibility state instead.
- Use more precise terms when laying out the same-origin requirements
  between the top-level traversable and its child navigables. The new
  paragraph is a mouthful, but also more precise.
- Instead of referring to the SECURE-CONTEXTS spec, use HTML's definition of
  "secure context".

This change should not cause any behavioral or user-detectable changes.
@rakuco rakuco requested a review from reillyeon October 30, 2023 15:05
@rakuco rakuco merged commit 5e62e4e into main Nov 7, 2023
2 checks passed
@rakuco rakuco deleted the update-event-firing-restrictions-wording branch November 7, 2023 09:52
github-actions bot added a commit that referenced this pull request Nov 7, 2023
…s" (#114)

SHA: 5e62e4e
Reason: push, by rakuco

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants