mdn/content

Be more accurate about cross-origin protections

Open

#23,740 opened on Jan 18, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Markdown (22,427 forks)batch import
Content:WebAPIarea: Performance APIeffort: mediumhelp wanted

Repository metrics

Stars
 (8,900 stars)
PR merge metrics
 (Avg merge 7d 3h) (147 merged PRs in 30d)

Description

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Resource_Timing_API

What specific section or headline is this issue about?

No response

What information was incorrect, unhelpful, or incomplete?

  • Timing-Allow-Origin is needed for CORS and no-cors, it's for cross-origin protection
  • In the case of cross-origin iframes, responseEnd might measure when the iframe finished loading completely with all its subresources, not just the main resource.
  • encoded/decoded body size are (soon to be) CORS-protected rather than TAO protected

What did you expect to see?

See above

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Contributor guide

Research direction
Review the current documentation at the given URL and confirm the inaccuracies. Update the page to specify that Timing Allow Origin is needed for CORS and no cors, clarify that responseEnd might measure iframe loading, and note that encoded/decoded body size are now CORS protected.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitMarkdown
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70