bug: Inconsistent State on Browser Back/Forward

[Aditya8369]

• Description: In App.jsx, the handlePopState effect updates the position and selectedCity from the URL hash. However, if the user navigates back to a state where there is no hash, it calls setSelectedCity("auto") but doesn't trigger the geolocation flow, potentially leaving the UI in an inconsistent state (e.g., showing the previous city's data but with "auto" selected).
• Fix/Enhancement: Modify the handlePopState function to explicitly trigger the geolocation flow when falling back to the "auto" state, ensuring the UI correctly updates to the user's current location.

[github-actions]

👋 Thank you @Aditya8369 for opening this issue!

We appreciate you taking the time to report or suggest an improvement for Pollution Control Hub.

Our maintainers will review your issue as soon as possible.

Meanwhile, please ensure:

• 📌 The issue clearly describes the problem or feature request.
• 📝 Steps to reproduce (if it's a bug) are included.
• 📷 Screenshots or logs are attached when applicable.
• 🔍 The issue is not a duplicate of an existing one.

Thank you for contributing to the project! 🚀

[sanjana2505006]

@Aditya8369 may i take this one?

[github-actions]

Issue is assigned to you, @sanjana2505006! 🎯

⏳ Note: Please submit a working PR within 3 days, else the issue will be unassigned and open for other contributors. 🚀

[sanjana2505006]

@Aditya8369
Looks like this is already fixed on main
handlePopState calls setDetecting(true) and startGeolocation() when there's no hash (commit 83d2133).
Happy to close this unless you're still seeing the stale-city case after that.