-
Notifications
You must be signed in to change notification settings - Fork 659
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
Title doesn't update when opening in a new tab until focused #315
Comments
I just realized that there's another issue related to this that was answered already: #314. TL;DR: add |
freiksenet
pushed a commit
to gatsbyjs/gatsby
that referenced
this issue
Jun 11, 2019
…sed (#14661) When opening a link from Gatsby site in a new tab (via cmd+click for example), the new tab title is not correctly updated from its default title. Related to: nfl/react-helmet#315 nfl/react-helmet#314
mxxk
pushed a commit
to mxxk/gatsby
that referenced
this issue
Jun 21, 2019
…sed (gatsbyjs#14661) When opening a link from Gatsby site in a new tab (via cmd+click for example), the new tab title is not correctly updated from its default title. Related to: nfl/react-helmet#315 nfl/react-helmet#314
johno
pushed a commit
to johno/gatsby
that referenced
this issue
Jul 17, 2019
…sed (gatsbyjs#14661) When opening a link from Gatsby site in a new tab (via cmd+click for example), the new tab title is not correctly updated from its default title. Related to: nfl/react-helmet#315 nfl/react-helmet#314
This solution still works, but it's not documented in the README. |
Was looking for this as well, thanks! |
scarf005
added a commit
to scarf005/iso8601
that referenced
this issue
May 19, 2023
scarf005
added a commit
to scarf005/iso8601
that referenced
this issue
May 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When opening a link from my app in a new tab (via cmd+click for example), the new tab title is not correctly updated from its default title. When selecting the tab, the title gets updated correcly.
It seems to be cause by the introduction of
requestAnimationFrame
in the pull request #307. At least in chrome,requestAnimationFrame
is not executed on background tabs.I've tested with a previous version (5.0.0), which has the correct behaviour.
(bug observed by @samuelmartineau)
The text was updated successfully, but these errors were encountered: