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

Add a sticky Scroll To Top button #2864

Closed
2 of 5 tasks
alinadivante opened this issue May 7, 2019 · 3 comments
Closed
2 of 5 tasks

Add a sticky Scroll To Top button #2864

alinadivante opened this issue May 7, 2019 · 3 comments
Labels
feature request Requests for new features. Please be as specific as possible and provide proposal API if it you can QA approved after merge Testers will add this label after positive check on merged changes
Milestone

Comments

@alinadivante
Copy link
Collaborator

What is the motivation for adding / enhancing this feature?

This feature gives better navigation and allow users to easily scroll back to the top of category page with one click of the button.

What are the acceptance criteria

Add sticky "Scroll to top" button on category page.

Can you complete this feature request by yourself?

  • YES
  • NO

Which Release Cycle state this refers to? Info for developer.

Pick one option.

  • This is a normal feature request. This should be available on https://test.storefrontcloud.io and then after tests this can be added to next Vue Storefront version. In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
  • (Pick this option only if you're sure) This is an important improvement request for current Release Candidate version on https://next.storefrontcloud.io and should be placed in next RC version. In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
  • (Pick this option only if you're sure) This is a critical improvement request for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version. In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Additional information

@alinadivante alinadivante added the feature request Requests for new features. Please be as specific as possible and provide proposal API if it you can label May 7, 2019
@pkarw pkarw added this to the 1.10.0-rc.1 milestone May 8, 2019
@RGijsberts
Copy link
Contributor

I will work on this

@pkarw
Copy link
Collaborator

pkarw commented May 10, 2019

@RGijsberts it seems like it's already done: #2866

@RGijsberts
Copy link
Contributor

@RGijsberts it seems like it's already done: #2866

I missed that, nice!

@alinadivante alinadivante added the QA approved after merge Testers will add this label after positive check on merged changes label May 16, 2019
@pkarw pkarw closed this as completed May 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new features. Please be as specific as possible and provide proposal API if it you can QA approved after merge Testers will add this label after positive check on merged changes
Projects
None yet
Development

No branches or pull requests

3 participants