To love Opera, or not to love Opera

My applying it to my browser will not help new users. It would need to be applied to the site stylesheet instead of the browser one so that everyone can see it.

Oh, I know :slight_smile: I pinged Hawk and orodio to it so hopefully we can get that done. :smile:

@felgall the Discourse Team did say at meta that they would consider PRs.
If you have the time and inclination and have some know-how re Ember maybe you could do some Opera fixes.
Even if Discourse doesn’t take them into the Core I think there would be a very good chance that they would be used here.

important is only needed if it’s not showing up : ) If there’s a right declaration in the SitePoint code, you’ll need it for Opera as it does not honour user stylesheets over author.

Why my stylesheet for the buttons had many importants.

1 Like

I’d say you will eventually upgrade anyway, regardless. The number of websites Opera 12 is having trouble with is only going to increase.

You could go the route of petitioning opera. That’s not something I believe necessary. It never payed off for Opera to be the browser you appreciate. I’m optimistic it will pay off being Opera 24 and on, I am most content surfing the web with it, and that is a better start than keeping happy old users and their habits. Believe it or not, Opera does a lot of things right in the newer version, you just have to be willing to acknowledge them.

At this time you can only navigate form elements in Opera using keyboard shortcuts, so I believe a solution for the in-page links problem is on its way.

On the other hand, Opera 12 is old software by any account and if I can’t get for free nor build in the newer version old functionality that I like, by my own, then I’ll do what any normal user should do: cut my loses and use an up to date software.

It’s just using the Blink rendering engine. If it can’t give me some of the added usability old Opera 12 gives me, I have no reason to really step over to Opera, when I could just use Chromium and have exactly the same engine. Opera has always really defined itself as a browser by a specialty UI. If they keep that ethos, or add some mad privacy stuff, then there will be people preferring it to Chrome.

If that skip-link bug gets fixed, it gets fixed at the engine level, meaning it will be fixed for both Opera and Chrome/Chromium and whatever else, like Iron, using Blink.

Yes, but not the same browsing experience. And that’s why users like me keep preferring it to Chrome and that’s why Opera 24 and up will attract new users.

Among the top reasons I stepped over to Opera 24 are really good high DPI support against IE 11 and Firefox, improved UI against IE 11 and Chrome 37, fast and smooth against Firefox 34.

I would only Opera 12 is still the most advanced browser in existence - none of the others have a rewind button (there is an extension for Firefox to add that functionality but it doesn’t make sense to switch from the most advanced Opera 12 to the most primitive of the other popular browsers).

It seems to me that your concern over the web is not with web content but with client functionality. I seem to recall that content comes first.

Whatever browsing functionality Opera 12 has to offer, its serving and rendering of the current web content is sub-par to the “most primitive” (in your own opinion, of course) up to date browser. Firefox 17 predates Opera 12 and scores better at HTML support. Current Firefox version is 32 and scores way above Opera 12… but under Opera 24!

And I’m not just saying this. HTML 5 TEST puts Opera 12 at 392 and Opera 24 at 504. The gap is only getting bigger and bigger, since the over two years old Presto is not going to become anyone’s concern, not at Opera anyway. They are busy doing things users like me can appreciate.

Web content evolution won’t be put on hold, as Microsoft is not allowed to forget to this day, with its IE6 mishap. IE6 users were trapped. For the most of us Opera 12 will not be the new IE6, Opera 24 and up rocks!

Let’s also remember few years back Firefox users refused to transition and were still thinking of Firefox 3. Those voices are all lost now. The web has too much to look forward to.

Web sites should be concerned with providing CONTENT that people want to see. For web developers content comes first. Since content comes first it shouldn’t matter which browser is used to visit the site as even the original WWW browser can read web content. It is only the extras like images, audio, video, stylesheets, JavaScript etc that require more modern browsers. As long as your visitors can read the content all the rest is just a side dish (do you want a little CSS with that?).

When it comes to the browser that YOU use for YOUR web browsing the functionality of that browser is the ONLY thing of any relevance whatsoever. For web users functionality comes first, second, third, fourth and last - there is nothing else. People will always use the browser that they are happy with using and know how to use. Many will never consider switching at all because they don’t realise that alternatives exist while those with greater experience will choose the one that works the way they want.

Only Opera 12 has a rewind button. I use the rewind button almost as much as everything else in the browser put together. Therefore all of the other browsers are 0% compatible with my requirements regardless of anything else.

Anyway Opera still list version 12 as a current browser version as their replacement versions are still missing a lot of functionality. Only when the new Opera supports the rewind button will I have an upgrade path from the browser I currently use.

If one of the other browsers wants my business then they should introduce a rewind button into their browser and I will consider the switch.

I estimate that I would need 50+ extensions to implement Opera 12 functionality in Firefox by which time the extensions would make the browser run so slowly as to be unusable. That’s how far behind Opera 12 that the current version of Firefox is in terms of functionality (they were the last browser to implement a built in debugger for example).

Anyway I don’t visit a great many sites on the web - I spend far more time creating web content than I do reading content created by someone else (ratio at least 10 to 1). I test my content across all modern browsers but the only browser that provides the functionality I use when viewing other sites is Opera 12.

Any site that fails to support Opera 12 until a replacement browser offering the functionality I require will simply lose me as a visitor - there are enough other sites out there offering the same content that I will always be able to find somewhere to get the information from. It isn’t like I try to access anything fancy - most of the sites I visit I wouldn’t miss anything if I had images turned off.

So current browser scores from my viewpoint regarding usability for serious web browsing:

Opera 12 - 90%
Firefox - 2%
Opera 24 - 0%
Chrome - 0%
Internet Explorer 0%

The choice is obvious.

1 Like

No, Opera_24.0.1558.61 is listed as the latest and stable. Don’t spread misinformation.

The web is not what it used to be anymore. Content and content consumption now comes in many different shapes and forms. Opera 12 was simply not relevant enough 3 years ago and so Opera 12 has no chance of being even remotely relevant right now. That’s the reality. I wish you good luck in finding that rewind button. My guess is, if you take the plunge and get over Opera 12, you’ll find that liberating.

1 Like

You don’t have to wait for the browser of your dreams because some facts can be predicted easily now: there will never be a browser with a rewind button. Browsers tend to get rid of buttons and other UI elements and especially such a specialist feature like “rewinding” has absolutely no chance of finding its place in any browser. The only solution is waiting for someone to write an extension for that or write an extension yourself. I’ve never used a rewind button so I cannot image how useful it can be - I have found I can use a mouse gesture extension in Firefox/SeaMonkey that has the rewind option so I may try and see what’s so wonderful about it…

As to Opera 12 - it’s already dead, unfortunately, I’m not happy about it but we have to adapt. Its engine is still quite capable so it can be usable for some time but eventually its age will kill it. And there doesn’t seem to be any other browser to replace it even remotely since the tendency is to dumb down and simplify browsers so the only option now is to use extensions. Just like there’s no good old Opera, there are no more sitepoint forums that simply worked in all browsers. Hey, the world is changing!

I am not spreading misinformation.

Opera 12.17 is also listed as current and stable - and has many features that are missing from version 24.

When I click the “Check for Updates” button in Opera 12.17 I get a response “You are running the latest version”.

Opera 12 and earlier is a completely different browser to the ones numbered 15 and later - you may as well say those using Opera 24 should upgrade to Internet Explorer 11 as those two browsers have more in common than the two completely different Opera browsers do.

Opera 12 works perfectly well for all of what I want to do on the web and so I have absolutely no reason to upgrade. The loss of the button I use most would be the opposite of liberating - it would mean that I would not be able to use the web the way I want and so since there is little on the web I am actually interested in reading I would say that I would be more likely to give up reading anything on the web and just use it for creating content than I would be to switch to a browser that is lacking the most important of all the functionality that my browser MUST have.

The only reason this came up at all is that this site does not allow me to edit posts using the mouse because of a flaw in the way the site code works. I can still edit posts using the keyboard so it is a minor inconvenience - as opposed to the major disruption not having a rewind button.

If you want me to consider switching to a different browser then create a rewind button extension for that browser and I will consider it. Personally I am quite happy with Opera 12 which is still so far in advance of the other browsers in functionality (even though they are copying that functionality as quickly as they can) that it will probably be several more years before they catch up even if there are no new features added to Opera 12 in the meantime.

Opera has always been a relevant browser because it introduced most of the features the other browsers now have years before those other browsers decided to copy those features. For Opera to stay relevant they need to keep adding new features for the other browsers to copy. Opera 15 through 24 are not relevant because they are behind in features rather than ahead. About 99% of web users are using features in browsers that were originally introduced in Opera before being copied by the browser they are using so without Opera ALL browsers would be far different than they would be if Opera wasn’t there to copy features from.

Same here.

This cat fight has to stop!

http://images.sodahead.com/polls/002855881/4956448119_opera_wallpaper12_xlarge.jpeg

Thanks for the list!
None of those things (except Firefox having issues : P) are reasons for me to step over. I only use IE because it works best with ZoomText (which means I’m stuck with IE9, not 11… 11 doens’t work with ZT), I use Firefox mostly because of NoScript (a really nice plugin that’s quite different from Ghostery and the sort), Chromium is my 90% developer browser (because my employer chose to use Google Mail and Drive so I don’t want that googley cookies, beacons, ads and channel IDs polluting my other browsers) with checking in the others whenever I make a major change…

Opera sort of became my “social” browser, I think because of the built-in IRC let me use the browser and then also have, in a tab, the HTML-WG and Mozilla Accessibility rooms open. And the keyboardability. Those are just too convenient, so likely as you say, I’ll stop using Opera when so many sites are broken in it. The rendering engine should age well, but the whatever-I’m-using-post-Futark Javascript engine will not. As more ES6 gets backported into the Javascript used by browsers, Opera 12 will start seriously not working.

Again, though, what really separates browsers nowadays is what they offer the user, rather than how they render the pages (as @felgall said). So it’s things like the debuggers, or the functionality, or privacy claims, or sandboxing tabs, or whatever that will drive at least developer usage.

Regular people will go by how easily they can find something they need to do. Browsers really shot themselves in the foot when they thought it was such a great idea to hide everything behind a single button or keyboard shortcut. They’re also shooting themselves when hiding parts of URLs-- after banks spending the last 10 years warning people to check for https, most browsers have effectively hidden that because vendors feel “people are stupid and may be frightened at strange-looking protocols”. No, you just made it easier to phish them, yay.

That kinki image is just soooo Opera.

did you know they have an official mankini? I heard it directly from Bruce himself.

To sum it up, for me it was three things:

  1. Speed
  2. Rendering
  3. Improved UI

over all three of them, including Chrome. Again, Opera 24 is not a skin for Chrome, that’s a wrong thing to perpetuate.

I need and use only one extension, µblock. NoScript was taking too much of my time lately, with all the cloud and web fonts and CDNs. However, since security should be top of the list, I also use the avast! extension.

This is likely off-topic and I don’t mean to hijack the discussion.

A few years ago I was using YUI to collect data from site visitors to get an idea of what the common viewport dimensions were.

I also colllected User-Agent (I know) and noticed a lot of “Opera Mini”.

I’m assuming this is an entirely different browser altogether?

Yes, Opera Mini is a mobile variant of the desktop version. It is requesting pages using the Opera servers for preprocessing and compression.