Skip to content

Sticky header for navigation in mobile, desktop #26135

Open
@divyajyothi5321

Description

@divyajyothi5321
Contributor

Description (*)

Sticky header for mobile, desktop versions

Expected behavior (*)

It will be easier for user to navigate the categories (using sticky menu) at any position in the page.

Benefits

It is a smart navigation that fixes the menu to the top of screen as the user scrolls down a page.

Additional information

It improves user experience

Activity

m2-assistant

m2-assistant commented on Dec 19, 2019

@m2-assistant

Hi @divyajyothi5321. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
    Information on your environment
    Steps to reproduce
    Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@divyajyothi5321 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
    no

m2-assistant

m2-assistant commented on Dec 19, 2019

@m2-assistant

Hi @divyajyothi5321. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

    2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

    3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

    4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!


self-assigned this
on Dec 20, 2019
m2-assistant

m2-assistant commented on Dec 20, 2019

@m2-assistant

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

    2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

    3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

    4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

    5. Add label Issue: Confirmed once verification is complete.

    6. Make sure that automatic system confirms that report has been added to the backlog.

krishprakash

krishprakash commented on Dec 23, 2019

@krishprakash

Hi @divyajyothi5321. Thank you for report.
This looks like feature request/Improvement so need to confirm with team.
@sdzhepa please review the ticket info and give your feedback on this.
Thanks.

m2-assistant

m2-assistant commented on Dec 23, 2019

@m2-assistant

Hi @sdzhepa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

    2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

    3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

    4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

    5. Add label Issue: Confirmed once verification is complete.

    6. Make sure that automatic system confirms that report has been added to the backlog.

hitesh-wagento

hitesh-wagento commented on Jan 3, 2020

@hitesh-wagento
Contributor

HI @sdzhepa

Can I proceed with this new improvement?

Thanks

79 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area: UI FrameworkComponent: SalesEvent: mm20inIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedPartner: i95DevPriority: P2A defect with this priority could have functionality issues which are not to expectations.Priority: P4No current plan to fix. Fixing can be deferred as a logical part of more important work.Progress: PR in progressReported on 2.4.xIndicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S2Major restrictions or short-term circumventions are required until a fix is available.Severity: S3Affects non-critical data or functionality and does not force users to employ a workaround.Triage: Ready for TriageIssue is ready to me triaged with Product Managerimprovementpartners-contributionPull Request is created by Magento Partner

Type

No type

Projects

Status

Pull Request In Progress

Relationships

None yet

    Participants

    @ihor-sviziev@mrtuvn@gabrieldagama@sdzhepa@hitesh-wagento

    Issue actions

      Sticky header for navigation in mobile, desktop · Issue #26135 · magento/magento2