Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Add Extensions API blog post for documentId and friends. #3903

Merged
merged 3 commits into from
Nov 30, 2022

Conversation

dtapuska
Copy link
Contributor

@dtapuska dtapuska commented Oct 4, 2022

  • Instant Navigation adds additional fields documentId, parentDocumentId, documentLifecycle, frameType to help improve the experience for back/forward cache and prerendering.

https://deploy-preview-3903--developer-chrome-com.netlify.app/blog/extension-instantnav/

@netlify
Copy link

netlify bot commented Oct 4, 2022

Deploy Preview for developer-chrome-com ready!

Name Link
🔨 Latest commit f4ca076
🔍 Latest deploy log https://app.netlify.com/sites/developer-chrome-com/deploys/6387ce556a66f10009182c3c
😎 Deploy Preview https://deploy-preview-3903--developer-chrome-com.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@dotproto
Copy link
Contributor

@jpmedley, FYI I'm tagging you in on this PR a little early. I figure It might be worth seeing how it reads & flows.

@jpmedley
Copy link
Contributor

@dotproto,

Thank you! Much appreciated.

@jpmedley
Copy link
Contributor

@dtapuska,

The review Simeon asked me to do is very meta. When the text is locked I'll do a copy edit (review for typos, spelling, punctuation, etc.)

@jpmedley
Copy link
Contributor

@dtapuska, @dotproto

the structure of this looks pretty good. I made a few comments, but won't do a thorough edit until you you tell me the text is locked.

@dtapuska
Copy link
Contributor Author

@dotproto ping, PTAL

@jpmedley
Copy link
Contributor

jpmedley commented Nov 4, 2022

@dotproto Is there anything I can do to help you move this?

@dotproto dotproto added extensions Issues related to extensions documentation. content labels Nov 7, 2022
Copy link
Contributor

@dotproto dotproto left a comment

Choose a reason for hiding this comment

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

Added some suggestions to clean up the information presentation a bit. Once these are settled I think we're good for @jpmedley to take a final pass.

site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
@jpmedley
Copy link
Contributor

jpmedley commented Nov 8, 2022

@dotproto If you have no more comments, please approve this. I'll do my review then.

Copy link
Contributor

@dotproto dotproto left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@jpmedley jpmedley left a comment

Choose a reason for hiding this comment

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

Dave,

Nice article! Don't let the number of changes scare you. Most of these are to make the article consistent with the rest of the site.

Unfortunately, there are a few items, we need to give some thought to.

site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
Copy link
Contributor Author

@dtapuska dtapuska left a comment

Choose a reason for hiding this comment

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

Applied fixes

site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
tab only had one active page. This was always the one that was visible. If a
user returns to the previous page, the active page would be destroyed (Page B)
and the previous page in history would be completely reconstructed (Page A).
Extensions did not need to worry about what life cycle pages were in because
Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes

site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved

When a page transitions from either Back/Forward Cache or prerender to the
active state there will be 3 more events (but with *documentLifecyle*
being *active*).
Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

Comment on lines 169 to 189
```js
onBeforeNavigate -> onCommitted -> onCompleted
```
Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
site/en/blog/extension-instantnav/index.md Outdated Show resolved Hide resolved
Comment on lines 124 to 132
- `"fenced_frame"`: A special type of frame that is embedded inside other frames
(see [fenced-frames](https://github.com/WICG/fenced-frame))
Copy link
Contributor

Choose a reason for hiding this comment

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

The odds are about 1.5 million to 1 that this value can even be used on a particular site. (My numbers are based on metrics for Chrome and origin trials.) I was trying to convince you to remove this completely. How about just saying 'Reserved for future use'?

@dtapuska dtapuska force-pushed the main branch 3 times, most recently from 4b99c32 to 57a95fe Compare November 29, 2022 21:32
@jpmedley
Copy link
Contributor

@rachelandrew I think we're past the original publish date in our content request. When can this go up.

@rachelandrew
Copy link
Collaborator

@jpmedley does it work to publish this tomorrow (30th)? That way it goes out between new in Chrome (today) and the beta post (the 1st)

- Instant Navigation adds additional fields documentId,
parentDocumentId, documentLifecycle, frameType to help improve the
experience for back/forward cache and prerendering.
@jpmedley
Copy link
Contributor

We can do tomorrow. Let me change the date real quick. and get Dave to merge it.

@jpmedley
Copy link
Contributor

It looks like Dave already did that. I'll leave this open in a tab and merge first thing tomorrow.

@jpmedley jpmedley merged commit ad377c1 into GoogleChrome:main Nov 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
content extensions Issues related to extensions documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants