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!
HotCakeX I'm actually not sure if the panes not remembering their pin state is intended or a bug, so let me ask.
- HotCakeXDec 02, 2020MVP
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.
- eduardobragaxzDec 02, 2020Iron ContributorAn 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.
- josh_bodnerDec 03, 2020Former Employee
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!
- eduardobragaxzDec 03, 2020Iron ContributorIt does, that's what I'm saying. Maybe you guys should make it so that, when it's pinned, you can't close by clicking the button again.
- HotCakeXDec 02, 2020MVP
eduardobragaxz wrote:
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.it's not about closing favorites/history menus that open from the toolbar, it's the fact that when user chooses to use sidebar instead of the flyout experience, then it should be remembered, and Not require user to do this action every time, repeatedly, just to get sidebar.
If I want to use sidebar instead of flyout, then show me sidebar when I click on favorites button, why do I have to click on the pin icon again and again if I already chose to view the sidebar version.
- eduardobragaxzDec 03, 2020Iron ContributorI guess I see it in a different way. To me, pinning it isn't setting it to a new state, you're just pinning there. It's either pinned or not. You're not setting it to be shown like that, you're just pinning it, and when it closes, it assumes you don't need it pinned anymore.
I understand what you mean, but I don't agree that it should work this way.