Where is the "Recently closed tabs/Tab menu" button on the top right?
-
chewy last edited by
@chewy Case In Point: I just closed and opened opera to discover there was yet again another "micro" update, from 70.0.3728.106 to 70.0.3728.119. No documentation, no "readme.txt" and no mention in the "blog" what exactly changed. This is the kind of thing that frustrates and bewilders people.
-
-
chewy last edited by leocg
@sgunhouse Just for some clarification, I did what you suggest and checked out their blog. Yes, you are correct, there is a section discussing the "Recently Closed" functionality, touting the "usefulness" of the addition of the new feature. However, this blog looks to only highlight some of the major changes; it does not correspond or even attempt to look like a proper change log. Additionally, the shear magnitude of negative comments regarding this new feature makes me wonder if the devs truly do respond to the community. The comments are overwhelmingly negative and plead with the devs to just rollback this function to what it was. In any event, thank you once again for your help and information.
-
leocg Moderator Volunteer last edited by
@chewy Here: https://blogs.opera.com/desktop/changelog-for-70/#b3728.119
-
-
chewy last edited by
@leocg Thank you for this information!
However, I do have a followup question: How did you find this information? I've been to the root blogs.opera.com/desktop and can not find a link to all change logs.
Also, this change log lists identifiers for different changes, yet no way to lookup each identifier to explain in detail, what these issues/changes are. Is there a way to do this? It would be really helpful for the public (at least the people that have to support this browser for a company) to look up any given issue to see the history and understand how it was resolved. Case In Point: (Example) the changelog lists "DNA-87863 Parameter placing issue in all languages" - there is nothing more explaining this. What is this? What was effected? How was it fixes?
Seeing the ticket details would help in understanding these things.
-
-
chewy last edited by
@leocg I see. So if I wanted to see a changelog for an older build, I'd have to dig through the blog, find the corresponding post, open the post, find the link for the changelog and take it from there? Talk about convoluted!
Although the severe inadequateness of posting changelogs is out of your control, I do want to thank you for this information. -
cherryaa last edited by
Hold on, does the "recently closed" section only show three items? Can I increase this? Looked through Settings; couldn't see anything.
If you really refuse to bring back or adequately substitute this feature, then will you allow us to dock the sidebar on the other side of the screen? I'm right-handed and sweeping the mouse across involves more wrist-bending than is healthy on a frequent basis.
-
chewy last edited by
@leocg Also, as I mentioned, there is no context to the changelog. There is no way to look up the ticket or history of any item in the changelog. In some cases, there is no way to understand some of these one-liners at all. So although I can decipher some of the issues/feature changes, a lot it remains clouded.
Having the ability to look at a particular items ticket or history would be greatly beneficial. Bugzilla would be a great example of what I'm talking about. -
-
-
chewy last edited by chewy
Until Opera reverts the disastrous changes to the "Recently Closed" button, there is a far better solution. It closely resembles what Opera took away from the toolbar. It's in the Chrome Store and it's an extension called "Tab Restore" by Banana Sonna. It is almost identical to the old Opera function; it seems to work exactly as the old "Recently Closed".
I think that what the devs just don't get is that taking the user from a quick pulldown (that doesn't shadow out your current tab and window) to this new implementation, is what part of the problem is. They pull the user away from the tab they're on, shadow grey out the whole browser to show you the list is just too different to use like the old way.
I hope this helps!
-
leocg Moderator Volunteer last edited by
@chewy In many cases, just the title of the report is enough to understand what was fixed or introduced.
There are some that may be part of a parent task and that's why their titles may not make sense.
Opera is closed source and have partnerships with lots of companies, so opening the bug tracking system could be a problem.
Also, I'm not sure if people are ready for a public bts.
-
-
chewy last edited by
@leocg Yeah, I am very familiar with the closed source mindset. The fear of allowing people to see the good and the bad could make the "shareholders" nervous.
Thank you once again for taking the time to write about this. Unfortunately, we will have to rely of the benevolence of the devs and Opera to be a little more forthcoming and open about these changes. Perhaps they will even provide clear justifications to the people that actually use their software, why and how these changes come to be.
-
leocg Moderator Volunteer last edited by
@chewy Opera was never exactly known for its talks to their users. Maybe on the very beginning, when the Internet wasn't so popular and the community of users were much more smaller and more willing to have a serious discussion.
Nowadays, Opera has to be very careful to what they answer to not be misunderstood.
-
DBOPERA last edited by
Is there any truth to the rumour that this feature is currently available in Opera Developer and will be returning? It'd be useful to know because I am at the point of uninstalling opera and trying vivaldi
-
-
cfyzuk last edited by
@sgunhouse which build? Can't find any notes in latest stable or latest devs. Or I miss something?
