search

remix-run / react-router

Declarative routing for React
https://reactrouter.com
MIT License
53.13k stars 10.31k forks source link

[Bug]: history.listen not triggered on hash changes #11739

Closed Qearl2016 closed 4 months ago

Qearl2016 commented 4 months ago

What version of React Router are you using?

v5.1.5

Steps to Reproduce

Hi,We have one application, includes windows and mac.When I changed hash in this application, the page haven't any change. So, how can i feel the hashChange listener is used? Maybe the hashChange listener have some problem. When I open A page, and then open another page B, page UI haven't change. Our terminal engineer said, because the baseUrl haven't change, so don't trigger source reload. But I think, hash router don't need source reload, just hash change can change page. Could you please tell me what changes do I have to make to have the same result.

Expected Behavior

When I open A page, and then open another page B, page UI can change

Actual Behavior

When I open A page, and then open another page B, page UI can change

github-actions[bot] commented 4 months ago

:wave: @Qearl2016, we use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. For usage questions, please use Stack Overflow or Discord where there are a lot more people ready to help you out, or post a new question in the Discussions tab of this repository. Please feel free to clarify your issue if you think it was closed prematurely.