Apparently, the “Add current tab”/“Mark current tab as read” button has been moved from the top of the reading list to the bottom of it. Why? What was the purpose of this change? It’s not a good place for it, the previous button was perfect. At the very least, there should be a toggle for us to pick where we want it, but having it at the top was far more intuitive. I really do not like it at the bottom.
I agree one hundred percent. My button moved too and I’m not thrilled. I’d like to confirm something though. Is this for everyone now? Was it pushed in a certain build?
Is this normal behavior?
Devs, You REALLY shouldn’t move other peoples things around without asking first just because one of you happens to have autism.
I’m not sure if everyone has it or not, I haven’t tested on a different device as my laptop is currently not functional. But yeah, I’m not sure why they moved it to the bottom, it’s more movement and thus is less convenient. The idea of features and changes in software should be to increase convenience and productivity. Before, I could open the reading list, barely move my mouse to the right (I use the sidebar on the left side) and hit the button to add/mark as read. Now, I have to move the mouse all the way to the bottom of the browser screen, which just isn’t convenient or intuitive.
What I don’t understand is why everyone is STILL pretending like we don’t exist. We might need to figure this out ourselves.
@lorewright For starters, what version of Windows are you on?
I’m using an Windows 10 LTSB branch on my desktop and a Windows 10 LTSC branch on my laptop. The button has moved on both. AFAIK neither would be considered an ‘officially supported’ version of windows. Maybe that’s part of the problem.
How about you?
What version of Brave are you both using? On my end, in both Release, Dev and Nightly builds, I see the buttons where they always are:
Hi @Mattches, Thanks for getting back to us.
Right now I’m on Version 1.57.53 Chromium: 116.0.5845.114 (Official Build) (64-bit)
But first noticed this on Brave Version; v 1.57.47.
In your screencap “Mark Current Tab as Read” is on the bottom of your screen.
That’s the problem.
Until a week ago it was up at the top just beneath the address bar.
Has the button ALWAYS been at the bottom of the screen or was it moved in a recent update?
I have a very, very, very large screen and thus, needing to scroll all the way to the bottom to hit the button takes me quite a while. Hours, even. It’s just not very ergonomic.
Thanks for your reply. As Disgruntled said, the issue we have is that the add/mark as read button used to be at the top of the menu, which I found to be far more intuitive. Running my mouse all the way to the bottom of the menu doesn’t “feel” right to me, it’s not intuitive. That’s what we’re referring to. Thanks again for your reply.
I do understand both of your points. My “argument” here would be that the button shown here in the reading list itself also performs this same function, and is located at the top of the screen.
Does using this option not help with respect to usability?
Show me how that button magically transforms into a button that ADDS THE CURRENT TAB TO THE READING LIST.
Y’know what? Nevermind.
@lorewright I’m just going to make a folder on my bookmarks tab, Call the folder “READING LIST AT THE TOP OF MY BROWSER” and pretend this whole function never existed.
Maybe you should consider the same?
Oh yes, I definitely know about that button but it’s so small that it’s also not intuitive as the main way to mark a page as read. I use that particular button to mark old ones as read if I forgot to do so after actually reading the page, so that I don’t have to re-open that page to mark it as such.
Maybe an option to choose whether it appears at the top or bottom might be worth looking into? That way, whatever people prefer, they will be able to decide and stick with it.
@lorewright I will pass this along to our devs for consideration. I know that the reading list feature has some changes coming a little down the road. Thank you for your feedback.
Thanks Mattches, that’s all I ask is for the team to consider the feedback