-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
[MainUI] Closing Location/Equipment/Properties does load a wrong page in Milestone 4.1.0.M4 #2196
Comments
I can confirm it happens also on my openHAB 4.1.0.M4. |
This bug is very annoying. |
Fixes openhab#2196. Reverts openhab#2074. I have tried messing around with the browser history manually to fix that issue, however trying several approaches, none worked perfect. This is the best solution I could come up with, it at least remembers which tab you had opened when you navigate back to the home page from any other page. Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
@lolodomo: I have created a PR to fix that. |
Yes in fact there's a bug that occasionally occurred even before (I think many have experienced a "double-back" when going back), this is likely a bug in Framework7's router actually. |
Probably the bug in f7router has already been fixed, but our deps are really outdated ... luckily #2151 may help with that. |
Fixes #2196. Replaces #2211. The double back navigation was caused by: https://github.com/framework7io/framework7/blob/31f4c7065e8abe9b8b27f354de4e390a8cd584c0/src/core/utils/history.js#L56-L61 and `router.updateCurrentUrl()`, unlike the name implies, doesn't update `router.url` for some reason (maybe a bug?). ----- Signed-off-by: Yannick Schaus <github@schaus.net>
Best is to share a recorded video: https://drive.google.com/file/d/1p1DLw-PepDrYO34Kv9jeFX-wSX94riyO/view?usp=sharing
This only happens in 4.1.x Milestones (I have seen in 4.1.0.M3 and 4.1.0.M4). No issues in openHAB 4.0.4.
It always jumps back to the previous page that was loaded. Same in Location, Equipment or Properties-Tab.
Tested in Chrome and Edge with same result.
The text was updated successfully, but these errors were encountered: