@aleksod correct, that article is wrong (on more than one point). It looks like the journalist didn't actually use Opera before writing the article

@fjuk We don't 'choose' to limit this functionality. Unfortunately there are complicated legal restrictions around distributing support for H264 video decoding, and it comes down to 'we can't give you this functionality ourselves'.

Therefore we rely on others to give it to you. On Windows and Mac, it's the operating system that provides libraries that do H264 decoding, and Opera uses those. On Linux it's a bit more complicated, but it comes down to 'we use what Chromium uses except we can't give it to you ourselves'.

Unfortunately this means that now and then, when the library Chromium uses changes, Opera needs a certain minimum version of the library to be able to work with it. The rule of thumb is that Opera can always use a library if it's the same version as the Chromium version Opera is based on (check opera://about to see which Chromium it's based on), and sometimes older versions, depending on when Chromium last changed the library. Since the library changed in Chromium 67 / Opera 54, we currently can't use older ones.

While we are waiting for the stable package to be updated in Ubuntu's repositories, if you want a more official, Ubuntu-supplied up-to-date version of the codecs package, there's a package available for Cosmic Beaver which is already at Chromium 67. You can find it here: https://packages.ubuntu.com/cosmic/chromium-codecs-ffmpeg-extra .

We're aware of the issue and it'll be fixed in the next update to Opera.

For people struggling with automatic update, it's much easier to disable it like this (and easy to revert later too):

Open Terminal.app and write

defaults write com.operasoftware.Opera OPDisableAutoUpdate true

@gik-team: It's being worked on, we're resolving problems with video playback on content-protected steaming sites.

@johnd78: It's a bug, thank you!

@burnout426 This is correct, we could see from our statistics that the number of users actually using Instant Search was negligible, even despite its prominent place in the Sidebar and various attempts to hint users at its existence.

However, we got a lot of positive comments about the 'Search in Tabs' associated feature which was until now a more hidden part of Instant Search.

That's why we have - with some regret - removed Instant Search, but kept (and made more prominent) the search-in-tabs feature.

@pilgi3 I'm sorry, sometimes hard decisions need to be taken. I hope you'll still enjoy Opera's other features. And I'm also hoping that maybe an extension developer feels like reviving a floating search bar as an extension

defaults write com.operasoftware.Opera OPDisableAutoUpdate true

This should be what you're looking for :). If it worked, Opera will tell you "Update checker is disabled" when you go to Opera -> About Opera.

@andrew84: This is how it is very much designed to work - similar to the app switcher you have in your OS (Alt+Tab on Windows, Cmd+Tab on Mac) and also similar to how this feature already worked with a different UI in Opera before.

If you prefer to cycle tabs in visual order, you can do this - as before - by disabling the option "Cycle tabs in most recently used order" in settings.

@mrmatteastwood Install http://launchpadlibrarian.net/345863538/chromium-codecs-ffmpeg-extra_62.0.3202.94-0ubuntu0.16.04.1317_amd64.deb (you can upgrade it again to the most recent version once Opera 51 stable has been released).

The problem is that Chromium was updated to 64, and the chromium-codecs-ffmpeg-extra package that comes with Chromium 64 only works with Opera >=51.

The other way around as well: Opera 51 will only work with chromium-codecs-ffmpeg-extra >=64, so once Opera 51 has been released and you've updated, you'll have to upgrade this package again.

Hi @jc1742, the removal of the text encoding menu follows a similar move by the core of Chrome, on which Opera is based. You can read more about the decision and its effects in Google's bug tracker here: https://bugs.chromium.org/p/chromium/issues/detail?id=597488 .

I don't see any extensions in Opera's collection right now that would allow you to change it, but there's an extension to install Chrome extensions here: https://addons.opera.com/en-gb/extensions/details/download-chrome-extension-9/?display=en

After installing that you should be able to use: https://chrome.google.com/webstore/detail/set-character-encoding/bpojelgakakmcfmjfilgdlmhefphglae?hl=en which is an extension allowing you to change text encoding.

@propheta Alright, thanks. It is on for some people who are in a test group, so I thought we could narrow down the cause if you happened to be in that group.

Could you make a video of the freeze happening and upload it somewhere to get a better idea of what you're seeing on your end?

Is address-bar-dropdown-cities enabled for you in opera://flags?

If so, could you disable it (and re-enable address-bar-dropdown-categories) to see if that's where the problem is?

@andrew84: Can you say when this feature gets in the way for you?

@andrew84: Can you describe these issues (or show a video)?

@johnd78: It's a bug, thank you!

@darkchaplain: Thank you, we've reproduced the bug with keyboard shortcuts. It has been reported as DNA-98231.

@darkchaplain: A setting for it has been implemented, it wasn't in time for this developer release but you'll see it next time.

It's killing my workflow multiple times a day, especially since just hovering the mouse in the wrong spot disables keyboard shortcuts.

This is a bug, can you expand a bit on this? What platform are you on and which keyboard shortcuts get disabled?

@andrew84:

I can suspect that if the enhanced address bar is enabled in Settings and Address bar dropdown categories is enabled by default there are two panels appear at the same time(Dropdown categories over the BABE , that's why it looks flickering while appearing)

This is not the issue. The flickering is happening because suggestions are coming in and being added to the view while the view is already shown.

@andrew84: You're right, it's a bug that the dropdown is not respecting the setting. It's known and the next update you'll get should have it fixed.

@andrew84: enhanced address bar (displaying a dropdown with suggestions on address field focus) will stay optional and a setting.

The dropdown itself won't be - no way we're going to support two dropdown implementations because you don't like the calculator