We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://w3c.github.io/navigation-timing/#marking-navigation-timing has step 11:
Set navigationTimingEntry's not restored reasons to the result of creating a NotRestoredReasons object given document's not restored reasons.
Note that create a NotRestoredReasons object takes a not restored reasons backingStruct and a realm, so this should probably pass the right realm. This should probably also link creating a NotRestoredReasons object to https://html.spec.whatwg.org/multipage/nav-history-apis.html#create-a-notrestoredreasons-object.
create a NotRestoredReasons object
not restored reasons backingStruct and a realm
creating a NotRestoredReasons object
Also, for some reason that last link in step 11 is to this spec's not restored reasons, but it should probably link to https://html.spec.whatwg.org/multipage/nav-history-apis.html#nrr-struct instead.
not restored reasons
The text was updated successfully, but these errors were encountered:
clelland
No branches or pull requests
https://w3c.github.io/navigation-timing/#marking-navigation-timing has step 11:
Note that
create a NotRestoredReasons object
takes anot restored reasons backingStruct and a realm
, so this should probably pass the right realm. This should probably also linkcreating a NotRestoredReasons object
to https://html.spec.whatwg.org/multipage/nav-history-apis.html#create-a-notrestoredreasons-object.Also, for some reason that last link in step 11 is to this spec's
not restored reasons
, but it should probably link to https://html.spec.whatwg.org/multipage/nav-history-apis.html#nrr-struct instead.The text was updated successfully, but these errors were encountered: