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.

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

NavigationOption: ScrollAfterNavigation:false => Prevents scroll after navigation #36605

Closed
Bartmax opened this issue Sep 16, 2021 · 4 comments
Closed
Labels
api-suggestion Early API idea and discussion, it is NOT ready for implementation area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one

Comments

@Bartmax
Copy link
Contributor

Bartmax commented Sep 16, 2021

When links have href to another page like for UX experience so user can copy url and share etc.
Let's say url:
/faq/1

it loads a faq page with collapsible items and dynamic question/content related info.
If you click on a link to /faq/2 it may be desired to prevent scrolling to the top.

NavigationManager.NavigateTo(@($"/faq/{id}"),new NavigationOptions () { ScrollAfterNavigation:false });

Pretty sure the functionability it's almost all already implemented on this PR.

There's a comment on that PR that also asks for the same thing.

@Bartmax Bartmax added the api-suggestion Early API idea and discussion, it is NOT ready for implementation label Sep 16, 2021
@Pilchie Pilchie added the area-blazor Includes: Blazor, Razor Components label Sep 17, 2021
@mkArtakMSFT mkArtakMSFT added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label Sep 20, 2021
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Sep 20, 2021
@ghost
Copy link

ghost commented Sep 20, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@javiercn javiercn added the jcn-p2 label Nov 5, 2021
@jirisykora83
Copy link

Any progress on this?

@ghost
Copy link

ghost commented Oct 12, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@MackinnonBuck
Copy link
Member

Closing this in favor of #40190

@MackinnonBuck MackinnonBuck closed this as not planned Won't fix, can't repro, duplicate, stale Nov 7, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api-suggestion Early API idea and discussion, it is NOT ready for implementation area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one
Projects
None yet
Development

No branches or pull requests

6 participants