In developing countries like Nigeria, Opera Mini is used by up to 70% of users on mobile.
This is a collection of front-end development features not supported by Opera Mini and, more importantly, some crowdsourced workarounds for them. This isn’t about bashing the problem, but figuring out the solution.
Read the blogpost: WTF Opera Mini?! | bitsofcode
Way to go, @ireaderinokun 
Nice one. But the truth is if most of these missing features were implemented, there won’t be need for the “MINI”. It probably would be another Webkit based browser.
The smart quip or the well written article?
i was kinda rushing and my eyes failed me , that was meant to be a reply to @IkoroVictor not the OP’s post,
Beginning to think it was a mistake not to post the text of the article itself. Oh well.
no it wasn’t… i did read the post, i definitely wasn’t trolling 
NB: I actually read it
I read her post but I made a point similar to @IkoroVictor’s when I first came across the project. It’s a good project, and honestly I feel weird even criticizing but Opera Mini doesn’t implement these things for a reason. For instance, line-height isn’t supported because a) it uses system fonts and also
Mini does not support the line-height CSS property at present, since testing showed that it generally meant less text fitted on any individual page, requiring more scrolling from the user. As a result, using line-height to position things vertically will not work.:
So, finding a workaround for this feature is kind of moot. Text decoration beyond underline is not supported by MOST browsers. Things that require redrawing the canvas like animations and transitions are not going to happen ever.
Most of what OM doesn’t support is aesthetic(see: unnecessary)/heavy and the idea is for it to be as light as possible. It’s not a WTF situation. They’re done that way intentionally.
The thing is your site can’t and doesn’t need to look the same across all browsers. Especially OM, which people use with the expectation that they’re getting compressed web pages. It just needs to presented well, and have good UX.
With all that said though and this is important, if your page is exceptionally broken in Opera Mini, it’s most likely it wasn’t built well to start with because the browser supports a lot more than it doesn’t.
It may seem good to find workarounds but it will affect those who are using screen readers. So usability and maintenance will all pay for these workarounds.
Anyone tried making an online payment using Opera Mini.
From my last experience I got a message on the WebPay module that Opera Mini was not supported.
Has there been any change with this?
there is Opera and Opera mini, (for the j2me phones and smartphones) owned by the same company > i think.
Opera App fixed all issues and set backs opera mini had, are we aware of this?
i use both of the browsers, Mini when i want to economise browsing data and opera if there’s alot of internet data and I want to have a seamless browsing experience.
Exactly the reason they have two versions!
Opera has a server which pre-processes the webpages,compresses images and removes animation.It also handles javascript as normal page loads, all with reason.
Imagine loading up a full webpage on your 128 x 160 Nokia c1, or 3110 j2me phone, or even the old Tecno p2 android 2.2 android phone. You can agree that it would not be practical.