-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
Website keeps redirecting me to v0 #17637
Comments
It seems expected. Only v0 uses this anchor navigation approach. |
Well, it's not what I expect, though. Still, I think that for the homepage this behavior should be changed because I expect that I'm not the only one who has old version bookmarked. |
What about the people that intentionally bookmark docs for v0? |
@eps1lon I think that a bookmark on the v0 subdomain is better. This redirection was most useful 1 year and a half ago when we first released v1. I won't object if we remove it at this point. However, I don't matter much either way, I don't expect a significant difference. |
My idea is to remove redirect only from the home page, not from other pages. As it makes sense, indeed, that people might've bookmarked old docs and are still using them. |
My proposal, we kill the redirection next year. But a large part of the traffic uses this redirection logic: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I believe the timing to kill the redirection is right (fewer users + there is a viable alternative) #17637 (comment) |
Current Behavior 😯
When I visit https://material-ui.com/#/ it redirects me to https://v0.material-ui.com/#/ every time
Expected Behavior 🤔
I don't want to be redirected to the old version.
Steps to Reproduce 🕹
Steps:
Your Environment 🌎
I'm using stable Chrome 77.0.3865.90 (Official Build) (64-bit) on CentOS 7
Cookies for material-ui only have Google Analytics. Opening in Incognito mode results in the same behavior.
The text was updated successfully, but these errors were encountered: