Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Client-side router does not correctly update RSS link in <head> on navigation #18209

Open
simevidas opened this issue Jul 25, 2022 · 1 comment
Open

Client-side router does not correctly update RSS link in <head> on navigation #18209

simevidas opened this issue Jul 25, 2022 · 1 comment

Comments

@simevidas
Copy link

simevidas commented Jul 25, 2022 •
edited

Describe the bug

The <link rel="alternate" type="application/rss+xml"> element in <head> is not correctly updated when the user navigates the website https://dev.to/.

To Reproduce

  1. Open https://dev.to/dashboard
  2. Using the browser’s devtools, observe that there is no <link rel="alternate"> element in <head>
  3. Click one of the Followers/Following… tabs in the side bar and then click any user to open their user profile page
  4. Observe that there is still no <link rel="alternate"> element in <head>
  5. Click the browser’s reload button to reload the page (this reboots the web app)
  6. Observe that there now is a <link rel="alternate"> element in <head> that points to that user’s RSS feed

Expected behavior

In step 4, the user’s RSS feed <link> should already be present in <head>. The site’s client-side router should add it during the navigation.

Desktop (please complete the following information):

  • OS, version: macOS 12.4
  • Browser, version: Firefox 104
@github-actions
Copy link
Contributor

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.

To our amazing contributors: issues labeled bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@simevidas