Forum Discussion
*UPDATED* Dev channel update to 88.0.705.9 is live
Hi,
I've sent feedbacks about this before but this seemingly small thing hasn't been fixed yet.
so you've added History and Favorite buttons to the Edge toolbar and we can pin them to turn them into sidebar.
the problem is, after pinning them and then closing them, they revert back to the "unpinned" state next time we click on their icons.
this shouldn't be happening, the pinned/unpinned state needs to be remembered.
it was discussed in the forum before and people want the same thing too. I've done my share by sending feedback but I really think if a request or feedback makes sense, it shouldn't be required for lots of people to send it in order for Edge team to act upon it. because it keeps others waiting.
even if 1 or 2 persons send something as feedback, and you evaluate it and see it makes sense, it's not a radical change, then it should be enough in certain cases IMO.
also not everyone can send feedback to Microsoft as you know, for e.g. when their diagnostics and feedback data are controlled by their private organization.
example of feedbacks that make sense and are not radical:
- making pinned/unpinned state of favorite/history/downloads(soon?) remembered and not lost after closing.
- show the true default value or flags (enabled or disabled)
and as always thanks for the update!
- Favorites and history should be grouped as one thing with a different heading like we had in internet explorer especially if we want it to be a sidebar thing.
ethanmenzel@josh_bodner I'll take this a step further. It should be easy to switch between each of the navigation focused side bars including collections, favorites, and history. How this switch is presented in the UI I can leave to others. My suggestion is to make the label in the upper left that today, the single word Collections, Favorites, and History, become a control with a down arrow to allow a quick switch between these three and anything else that is appropriate.
Rich
HotCakeX Okay, it looks like we're actually tracking the favorites/history collapse state very closely to see how many people repeatedly pin it since we intentionally aren't remembering the collapse state. The data will tell us whether or not we should change the default behavior.
josh_bodner I have some concerns about the metric you are monitoring. I am one of the people who supports remembering the pinned state. But since it doesn't work that way at the moment, I am not pinning favorites. In my case the current behavior discourages me from taking the action that seems to be the metric for how much people want this feature and I will not show up as someone who is repeatedly pinning favorites. But I may not be understanding how the metric is defined.
- Thanks that's good to know, hopefully it will result in a good user experience.
in my case, when I see it takes so much time, I just use the arrow on favorites bar until that changes.
HotCakeX I'm actually not sure if the panes not remembering their pin state is intended or a bug, so let me ask.
josh_bodner wrote:HotCakeX I'm actually not sure if the panes not remembering their pin state is intended or a bug, so let me ask.
Thanks, I really hope it's not intended, because that'd be wrong..
also the new favorites and history buttons take too long to show their contents and requiring user to wait that long, and then click on the pin icon, every single time again, and wait some more for the sidebar to appear.. not useful.
- An easy fix would be to not let us click the favorite/history button for it to close, then you'd be forced to click on the "x". Because when they're just floating over the page, clicking again on their respective buttons will close and reopen, and that doesn't happen when the pane is fixed. It just closes. To me it doesn't make much sense for it to remember if it was pinned or not.
eduardobragaxz In my Canary install, clicking the button again does close the pane, regardless of whether or not it's pinned, so if you have Canary too, you might check there to see if yours does the same. If so, it should be in the next Dev!
