Using MDBDropdownItem causes Hot Module Replacement


Topic: Using MDBDropdownItem causes Hot Module Replacement

Mike.Thomson asked 4 years ago

I am using navbar component with Drop down menus in my application. When I use MDBDropdownItem to direct to a different react router path, there is an unwanted delay and chrome console is cleared with message [HMR] Waiting for update signal from WDS...

If I replace this with MDBNavLink, I dont get the same problem, however the drop down menu remains on the screen. I can make this menu hide by making it have a class of d-none (using context API and onClick event) but then I need to press the NAVlink twice to make dropdown menu appear again.

Any suggestions?


Piotr Glejzer staff commented 4 years ago

do you have some examples of this?


Please insert min. 20 characters.

FREE CONSULTATION

Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.

Status

Open

Specification of the issue
  • User: Free
  • Premium support: No
  • Technology: MDB React
  • MDB Version: 4.27.0
  • Device: PC
  • Browser: Chrome
  • OS: Windows
  • Provided sample code: No
  • Provided link: No
Tags
hmr