Opera 69.0.3638.0 developer update

[A Former User]

A Former User @leocg last edited by A Former User

@leocg I think you'd have a high chance of remembering or finding out a forgotten website if you have smaller list to look at.
What I've noticed is Opera forces a lot of things onto it's users for no good reason. Forcing users to adopt the half-baked sidebar for the feature that they took away from the usual location.
Restricting users from picking their own search engines and forcing popular geo-located search engines instead. (Note: Popular doesn't mean good.)
Among other things like poor choices of features.
Forcing exception lists in the adblock.

I could go on but the likelihood of Opera changing any of it is tiny or even address it. Especially since most of these have been asked by many users over the years.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@artexjay Well, if we are talking about a small list of recently closed tabs, then the one in Menu > History would be enough.

[A Former User]

A Former User @leocg last edited by A Former User

@leocg more button clicks is not a good thing. Still not a good argument for the change that Opera has done.

I also like that you ignored quite a few of the things i mentioned. Smarter positioning for example, or not restricting users so much.

[andrew84]

andrew84 @leocg last edited by

@leocg said in Opera 69.0.3638.0 developer update:

More switches means more code that means more bugs

Following your logic it's also possible to say 'more features means more code that means more bugs'.
So let's clean up Opera browser from features and the code will be reduced twice maybe, and bugs as well.
But it should be taken into account, that most of the users use Opera because of handy
features. And if there are already many complaints about the removed feature and there were almost zero requests about removing the feature, this feature can be named as 'handy'.
What does really mean more cost keep the code this is removing/changing features and later returning the features back or implementing features that nobody will use.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@artexjay Usually you add something new to a product or service in order to try to bring more new users and keep the current ones.
So, although I understand your point, adding new features will always be necessary. And the removal of those that have no impact anymore too.

[A Former User]

A Former User @leocg last edited by A Former User

@leocg Well then they shouldn't deliver either ill thought out features or half-baked ones as they have a record of doing so.
For example the sidebar messanger features although a good idea would be better if it you could pin a website and access it through the sidebar. Especially with the rise of PWAs this would make lot more sense.
Or another example (I understand they need the money but come on) continue bookings and shopping sections. Is that really necessary? I don' think so. Normally youd either bookmark or pin those sites that you haven't finished looking at.

What Opera needs is to learn how to think and get rid of old unused features such as the search box as well as remove the idiotic restrictions they have on the browser. Trust me they would be removing tons of lines of code making it easier to work with and add more useful features. At the moment Opera is filled with bloated/half-baked features that for the most part people disable. They also need to learn how to identify used/liked features so that they keep it and continue enhancing and building it up instead of getting rid of it and getting anger from their users from it.

[avmon]

avmon @leocg last edited by

@leocg Ok, we don't need the full list of recently closed tabs but we do need a quick way to access them like before. There can be multiple reasons for wanting to frequently open a closed tab, for example, because of the little difference between the active tab and the rest in dark mode, which has led me to accidentally close them.

[xantares]

xantares last edited by

With this build Opera starts with the CSS media query prefers-color-scheme: dark seemingly returning true, although Opera's light theme is selected. (You can see it on web pages using mentioned media query, internal error pages being some of those.)
Toggling →dark →light in quick settings ends up with the prefers-color-scheme flag being evaluated correctly.
[Win10/64bit]

[l33t4opera]

l33t4opera last edited by l33t4opera

New build - Opera developer 69.0.3645.0 ;-)
The change log, and the announcement.

[ralf-brinkmann]

ralf-brinkmann @l33t4opera last edited by

@l33t4opera Webpage not available.

[l33t4opera]

l33t4opera @ralf-brinkmann last edited by

@ralf-brinkmann Hi Ralf, most probably some temporary issue, it worked fine for me today ;-)

[A Former User]

A Former User @leocg last edited by

@leocg I'll assume you agree with what i have said then.

[leocg]

leocg Moderator Volunteer @Guest last edited by

@artexjay Not necessarily.