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

Navbar Break Points - Disappearing Elements at Certain Widths #16

Closed
mj1268 opened this issue May 24, 2020 · 2 comments
Closed

Navbar Break Points - Disappearing Elements at Certain Widths #16

mj1268 opened this issue May 24, 2020 · 2 comments
Labels
question Further information is requested

Comments

@mj1268
Copy link

mj1268 commented May 24, 2020

Version

1.1.0

Reproduction link

https://github.com/mj1268/ArgonBugReport-NavbarCollapse

Operating System

Windows 10

Device

Laptop

Browser & Version

Google Chrome Version 81.0.4044.138 (Official Build) (64-bit)

Steps to reproduce

  1. Adjust width of window
  2. When adjusting past each breakpoint, observe when the NavItems disappear/reappear - independent of the appearance of the collapsed toggle hamburger menu

What is expected?

Expect elements of Navbar to be swapped out with the toggle menu as the screen size passes the specified breakpoint (elements disappear, toggle menu simultaneously appears at the same screen width).

What is actually happening?

  1. Elements of the Navbar are disappearing after certain breakpoints, but before the toggle menu appears, leading to no visible navigational items in certain screen widths.

Solution

Additional comments

This is my first time submitting a bug report, please let me know if there's any other info you need. Thanks!

@einazare
Copy link
Contributor

Hello there, @mj1268 ,

It seems to me that the product is working just fine.
Could you please share with us a video with your issue?

Best,
Manu

@einazare einazare added the question Further information is requested label May 26, 2020
@mj1268
Copy link
Author

mj1268 commented May 29, 2020

Okay, I actually was unable to replicate it myself. 😆

I think it was a build issue on my end somewhere along the way, I reinstalled the npm modules from scratch and it started working.

Sorry, thanks!

@mj1268 mj1268 closed this as completed May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants