w3c/navigation-timing issues and pull requests

#204 - Enum values that ignore naming conventions in Navigation Timing Level 2

Issue - State: closed - Opened by dontcallmedom-bot about 1 month ago - 1 comment

#203 - Support ReSpec dark mode.

Pull Request - State: closed - Opened by clelland about 1 month ago

#202 - Add `confidence` field to PerformanceNavigationTiming

Issue - State: open - Opened by mwjacksonmsft 4 months ago - 35 comments

#201 - "Create a NotRestoredReasons object" takes a realm, but "create the navigation timing entry" doesn't pass it

Issue - State: open - Opened by petervanderbeken 5 months ago

#200 - Fix `firstInterimResponseStart` name on diagram

Pull Request - State: closed - Opened by tunetheweb 5 months ago - 2 comments

#199 - Timing values are inconsistent across browsers when page is controlled by service worker

Issue - State: open - Opened by philipwalton 6 months ago

#198 - Update diagram to better reflect unload timing

Pull Request - State: closed - Opened by noamr 7 months ago

#197 - "Process Unload Event" in wrong place on timing diagram

Issue - State: closed - Opened by tunetheweb 7 months ago - 1 comment

#196 - Use correct ref for queuing

Pull Request - State: closed - Opened by noamr 8 months ago

#195 - Add notRestoredReasons to PerformanceNavigationTiming attribute

Pull Request - State: closed - Opened by rubberyuzu 9 months ago

#194 - Chore: Fix overloading in WebIDL

Issue - State: open - Opened by noamr 10 months ago

#193 - Proposal: add timestamp for when "activation" or "dismissal" starts

Issue - State: open - Opened by noamr 10 months ago - 2 comments

#192 - Consider using `reload` instead of `back_forward` for "tab restore"

Issue - State: open - Opened by noamr 11 months ago - 1 comment

#191 - Update diagram to make unload parallel

Pull Request - State: closed - Opened by noamr 11 months ago - 7 comments

#190 - Measuring `beforeunload`

Issue - State: open - Opened by yoavweiss over 1 year ago - 3 comments

#189 - Broken references in Navigation Timing Level 2

Issue - State: open - Opened by dontcallmedom-bot over 1 year ago

#188 - Add criticalCHRestart

Pull Request - State: closed - Opened by arichiv over 1 year ago - 13 comments

#187 - Fix some broken refs after navigation refactor

Pull Request - State: closed - Opened by noamr over 1 year ago

#186 - Broken references in Navigation Timing Level 2

Issue - State: closed - Opened by dontcallmedom-bot over 1 year ago - 1 comment

#185 - NavigationTimingType enum need updates as HTML spec changed

Issue - State: open - Opened by Elchi3 almost 2 years ago - 7 comments

#184 - Extending the NavigationTimingType

Issue - State: open - Opened by tunetheweb almost 2 years ago - 5 comments

#183 - performance.timeOrigin vs performance.timing.navigationStart

Issue - State: closed - Opened by Quadiago almost 2 years ago - 3 comments

#182 - Navigation timing name should be the initial URL

Pull Request - State: closed - Opened by noamr about 2 years ago - 1 comment

#181 - Clarify how PerformanceTiming.responseStart relates to Early Hint responses

Issue - State: open - Opened by colinbendell about 2 years ago - 5 comments

#180 - Extend 'NavigationType' to include User Agent Launch

Issue - State: closed - Opened by bmathwig over 2 years ago - 15 comments
Labels: enhancement

#179 - Detecting whether a navigation was BFCache-eligible

Issue - State: open - Opened by fergald over 2 years ago - 2 comments
Labels: enhancement

#178 - Extend the navigationType enum to include "reload after being discarded" navigations

Issue - State: closed - Opened by yoavweiss over 2 years ago - 3 comments

#177 - Report that Critical-CH was used to restart a navigation

Issue - State: closed - Opened by yoavweiss over 2 years ago - 5 comments
Labels: enhancement

#176 - Pass response body info through

Pull Request - State: closed - Opened by noamr over 2 years ago

#175 - Update diagram: rename "prompt to unload" and "AppCache"

Pull Request - State: closed - Opened by noamr over 2 years ago

#174 - Update "relevant application cache" to point to HTTP cache

Pull Request - State: closed - Opened by noamr over 2 years ago

#174 - Update "relevant application cache" to point to HTTP cache

Pull Request - State: closed - Opened by noamr over 2 years ago

#173 - Links to "relevant application caches" are broken

Issue - State: closed - Opened by yoavweiss over 2 years ago - 1 comment

#173 - Links to "relevant application caches" are broken

Issue - State: closed - Opened by yoavweiss over 2 years ago - 1 comment

#172 - Rename NavigationType to NavigationTimingType

Pull Request - State: closed - Opened by domenic over 2 years ago

#171 - Extend Navigation Timing API to include back/forward cache NotRestoredReasons

Issue - State: open - Opened by rubberyuzu over 2 years ago - 4 comments
Labels: enhancement

#170 - Hide redirectStart and redirectEnd for navigations with cross-origin redirects

Pull Request - State: closed - Opened by noamr over 2 years ago - 3 comments

#170 - Hide redirectStart and redirectEnd for navigations with cross-origin redirects

Pull Request - State: closed - Opened by noamr over 2 years ago - 3 comments

#169 - Should pages with different COOP be able to get unload event start/end.

Issue - State: closed - Opened by hemeryar over 2 years ago - 13 comments

#168 - Fix multiple lint warnings:

Pull Request - State: closed - Opened by noamr over 2 years ago - 1 comment

#167 - ToT spec has a bunch of respec warnings and errors

Issue - State: closed - Opened by yoavweiss over 2 years ago - 1 comment

#167 - ToT spec has a bunch of respec warnings and errors

Issue - State: closed - Opened by yoavweiss over 2 years ago - 1 comment

#166 - Reporting timestamps rely on a global object which might not exist yet

Issue - State: closed - Opened by noamr almost 3 years ago - 1 comment

#165 - Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows

Issue - State: closed - Opened by ThierryMajutec almost 3 years ago - 5 comments

#164 - Processing Model: Should 'prompt for unload' box actually be unload?

Issue - State: closed - Opened by andydavies almost 3 years ago

#163 - How should prefetch be exposed?

Issue - State: closed - Opened by jeremyroman almost 3 years ago - 7 comments
Labels: enhancement

#162 - Fix typo in markup

Pull Request - State: closed - Opened by clelland almost 3 years ago

#161 - Add a landing attribute to PerformanceNavigationTiming

Pull Request - State: open - Opened by yoavweiss about 3 years ago - 11 comments

#160 - Using navigationStart as a baseline may expose cross-origin timing information

Issue - State: open - Opened by noamr about 3 years ago - 69 comments

#159 - Add non-normative notes for attributes.

Pull Request - State: closed - Opened by noamr about 3 years ago - 1 comment

#159 - Add non-normative notes for attributes.

Pull Request - State: closed - Opened by noamr about 3 years ago - 1 comment

#158 - Clarify spec and tests with respect to redirect info

Issue - State: closed - Opened by npm1 about 3 years ago - 3 comments

#157 - Add non-normative explanations for each of the attributes and when they are set or unset

Issue - State: closed - Opened by npm1 about 3 years ago - 3 comments

#155 - Should about:blank have a PerformanceNavigationTiming?

Issue - State: closed - Opened by achristensen07 about 3 years ago - 7 comments

#154 - Lack of Feature Parity with Performace.measure() in Level 2

Issue - State: open - Opened by c3-ThomasHuo about 3 years ago - 5 comments

#153 - Fix the auto-publish

Issue - State: closed - Opened by plehegar about 3 years ago - 1 comment
Labels: w3c, admin

#153 - Fix the auto-publish

Issue - State: closed - Opened by plehegar about 3 years ago - 1 comment
Labels: w3c, admin

#152 - Improve processing model diagram by illustrating that unload happens out-of-sequence

Pull Request - State: closed - Opened by sgomes about 3 years ago - 4 comments

#151 - The unloadEventEnd attribute

Issue - State: closed - Opened by yujun-0127 about 3 years ago - 3 comments

#150 - Switch to GitHub action

Pull Request - State: closed - Opened by plehegar over 3 years ago
Labels: w3c

#150 - Switch to GitHub action

Pull Request - State: closed - Opened by plehegar over 3 years ago
Labels: w3c

#149 - The "Obsolete" label is rendered in a seemingly random place

Issue - State: open - Opened by Krinkle over 3 years ago - 12 comments

#148 - Add a test that ensures `fetchStart` matches the SW's fetch event start time

Issue - State: closed - Opened by yoavweiss over 3 years ago - 1 comment

#147 - Spec needs a serious rewrite

Issue - State: closed - Opened by marcoscaceres over 3 years ago - 5 comments

#146 - A scenario where transferSize is 0 for non cached loads (or may be not)

Issue - State: closed - Opened by Nithanaroy over 3 years ago - 11 comments

#145 - list of possible initiator types from the resource timing API?

Issue - State: closed - Opened by ThierryMajutec over 3 years ago - 3 comments

#144 - Clarify security context for PerformanceNavigationTiming

Issue - State: closed - Opened by fred-wang over 3 years ago - 6 comments

#143 - Integrate with service worker timing

Pull Request - State: closed - Opened by noamr over 3 years ago - 1 comment

#142 - Use real refs for DOM metrics

Pull Request - State: closed - Opened by noamr over 3 years ago

#142 - Use real refs for DOM metrics

Pull Request - State: closed - Opened by noamr over 3 years ago

#141 - Integration with the HTML spec

Pull Request - State: closed - Opened by noamr over 3 years ago - 1 comment

#140 - AppCache meaning

Issue - State: closed - Opened by ThierryMajutec over 3 years ago - 8 comments

#139 - Change editors

Pull Request - State: closed - Opened by yoavweiss over 3 years ago

#138 - Connection time missing after redirection...

Issue - State: closed - Opened by ThierryMajutec over 3 years ago - 2 comments

#137 - 4.2 Same origin check should have clear inputs

Issue - State: closed - Opened by yoavweiss over 3 years ago - 1 comment
Labels: fetch-integration

#137 - 4.2 Same origin check should have clear inputs

Issue - State: closed - Opened by yoavweiss over 3 years ago - 1 comment
Labels: fetch-integration

#136 - 4.1 Processing model should rely on Fetch/HTML

Issue - State: closed - Opened by yoavweiss over 3 years ago - 3 comments
Labels: fetch-integration

#135 - 3.3 Getters should not replicate processing model definitions

Issue - State: closed - Opened by yoavweiss over 3 years ago - 1 comment
Labels: fetch-integration

#134 - 3.2 workerTime definition

Issue - State: closed - Opened by yoavweiss over 3 years ago - 2 comments
Labels: fetch-integration

#133 - 3.1 duration definition should be done in a single place

Issue - State: closed - Opened by yoavweiss over 3 years ago - 2 comments
Labels: fetch-integration

#133 - 3.1 duration definition should be done in a single place

Issue - State: closed - Opened by yoavweiss over 3 years ago - 2 comments
Labels: fetch-integration

#132 - a bit confused with the "Redirect" timing in Time Navigation

Issue - State: closed - Opened by ThierryMajutec almost 4 years ago - 4 comments

#131 - workerStart and redirects

Pull Request - State: open - Opened by nicjansma about 4 years ago - 28 comments
Labels: hackathon_15_09_20, hackathon_2020

#130 - Use PP2017

Pull Request - State: closed - Opened by plehegar about 4 years ago
Labels: w3c

#130 - Use PP2017

Pull Request - State: closed - Opened by plehegar about 4 years ago
Labels: w3c

#129 - Point navigation type values to HTML spec's new history handling

Pull Request - State: closed - Opened by gi11es about 4 years ago
Labels: hackathon_15_09_20, hackathon_2020

#129 - Point navigation type values to HTML spec's new history handling

Pull Request - State: closed - Opened by gi11es about 4 years ago
Labels: hackathon_15_09_20, hackathon_2020

#128 - worker start needs to be added to diagram

Issue - State: closed - Opened by pauljroy about 4 years ago - 8 comments
Labels: hackathon_15_09_20, clarification, hackathon_2020

#127 - Respec errors

Issue - State: closed - Opened by yoavweiss over 4 years ago - 1 comment

#127 - Respec errors

Issue - State: closed - Opened by yoavweiss over 4 years ago - 1 comment

#126 - Possibility to get the HTTP status code from the Response Header ?

Issue - State: closed - Opened by ThierryMajutec over 4 years ago - 9 comments
Labels: enhancement

#125 - PerformanceNavigationTiming needs a realm

Issue - State: closed - Opened by npm1 over 4 years ago - 1 comment
Labels: clarification, fetch-integration

#125 - PerformanceNavigationTiming needs a realm

Issue - State: closed - Opened by npm1 over 4 years ago - 1 comment
Labels: clarification, fetch-integration

#124 - What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved?

Issue - State: closed - Opened by abhishekcghosh over 4 years ago - 11 comments
Labels: clarification

GitHub / w3c/navigation-timing issues and pull requests