3 ms·
That scenario is already handled (and arguably a lot better) by the middle mouse button and existing browser functionality.
by flukus 10y ago
That scenario is already handled (and arguably a lot better) by the middle mouse button and existing browser functionality.
- ClayFerguson 10y agolmfao. Maybe Microsoft Word hasn't figured out yet how much more usable Word would be if it scrolled you to the top every time you opened a dialog and closed it. That's hilarious.
- ec109685 10y agoBrowsers maintain scroll position when clicking back.
- ClayFerguson 10y agoAre you guys actually arguing that closing a dialog or popup in a web-app should be done with the back button? Or merely that the back button should DO that functionality? Once you write a true "application-like SPA" you see the flaws in the back button, for anything other than static docs, but unless you have the experience you won't "just get it". There's a reason no "back button" was ever invented for "desktop apps" and ONLY came into existence in web browsers browsing static docs.
- flukus 10y ago> There's a reason no "back button" was ever invented for "desktop apps" and ONLY came into existence in web browsers browsing static docs. It exists in quite a few dekstop apps (explorer and control panel on windows to name a couple). Android also has an ubiquitous back button.
- ClayFerguson 10y agoApps which have a meaning for "the previous place I was at", benefit from a way to go back. I do plan on a "back button" in meta64 that takes you to the prior NODE (and will be a full history of nodes), but this most definitely will not be a page refresh of the entire page. Will be a button INSIDE the app, just like all other APP functions. Meta64 is a mobile APP also, so relying on a browser-level back button is not an option.
- flukus 10y agoBrowsers maintain scroll position when you open a new tab.