#Needs product manager review

@effulgentsia we've had responsive image module in core for about ten years, it relies on the picture element, which Opera Mini does not support.

Given this, what do you think the concrete consequences have been of 'supporting' Opera Mini during this time, given it's never tested as part of a browser matrix, and what do you think the consequences would be of dropping support?

This press release from this month is still making the claim that Opera Mini has 100M users worldwide. Note that's a decrease from claims about 100M users in Africa.

It's possible that they're making a false claim, but if it's true, that's still 2% of the global internet population, and likely a significantly higher percentage in Africa if that's where they have a higher than average concentration.

@effulgentsia asked stats questions on #3510387-9: Replace "Opera Mini" with "Opera Mobile" in supported browsers → which I have tried to answer in the two comments after that one.

The short version is that with Opera Mini, it shows as 0.05% usage globally, but in Kenya, which has the highest sample size of countries that also have highest Opera Mini usage, it's hovering around 5%. Or in Nigeria down from 5% to 2.5% in the past couple of years.

I think we could add something like this:

"If a browser has disproportionately high usage in a specific region, then it can be removed if the usage on course to be below 5-10% in countries in that region by the time of the next major core release. One source of this data is regional statcounter reports."

This would then match the regional 30% language in 'adding a new browser'. I think it's probably good to have a gap between the threshold for adding a browser and the threshold for removing one, they shouldn't be too close otherwise it could lead to unnecessary churn.

Back to needs review for that bit. Should we move the suggested text into the issue summary too?

2024 data:

Nigeria: 2.93%
https://gs.statcounter.com/browser-version-market-share/all/nigeria/#mon...

Kenya: 4.84%
https://gs.statcounter.com/browser-version-market-share/all/kenya/#month...

Egypt: not shown
https://gs.statcounter.com/browser-version-market-share/all/egypt/#month...

Tanzania: 8.48%
https://gs.statcounter.com/browser-version-market-share/all/tanzania/#mo...

South Africa: not shown
https://gs.statcounter.com/browser-version-market-share/all/south-africa...

DRC: 3.8%
https://gs.statcounter.com/browser-version-market-share/all/congo-democr...

Ethiopia: not shown
https://gs.statcounter.com/browser-version-market-share/all/ethiopia#mon...

Sample sizes, appears to be from 2022:

United Kingdom: 224598472 vs 60m population (3.74/person) (for comparison)

Kenya: 10552834 vs 55m population (0.19/person)

Nigeria: 24886882 vs 220m (0.11/person)

Tanzania: 3593251 vs 60m (0.05/person)

Egypt: 28550683 vs 114m (2.5/person)

Congo: 1423417 vs 108m (0.013/person)

Ethiopia: 4079886 vs. 128m (0.03/person)

Congo, Tanzania and Ethiopia have unreasonably small sample sizes. If we exclude Tanzania, the highest usage is Kenya at 4.84%.

Kenya was 3.83% in 2022,5.39% in 2023, 4.84% in 2024. That isn't a trend, but it is hovering around 4-5%.

Statcounter says:

"Stats are based on aggregate data collected by Statcounter on a sample exceeding 5 billion pageviews per month collected from across the Statcounter network of more than 1.5 million websites. Stats are updated and made available every day, however are subject to quality assurance testing and revision for 45 days from publication."

We don't know what those 1.5m websites are but it's easy for them to be skewed towards particular countries in terms of audience, and therefore undercount visits from other countries.

Also page views % != unique people %.

I checked the faq, and they record more page views from the United Kingdom than from China despite 60m people in the UK and 1.4b in China.

https://gs.statcounter.com/faq#sample-size

For me that's more than enough to explain the discrepancy. However there's also the statcounter country specific data which shows a downwards trend for in Nigeria from 5% to 2.5% in two years (see issue summary).

If we temporarily pretend that page views percentage do actually represent percentage of people, that would be 2.5% of 200m people, which is 5m people in a single country not 3m people internationally. I didn't check the page view stats for Nigeria compared to the US, UK and China, it's in a csv linked from the faq though.

However 2.5% of the people (*page views) in one country on a downward trend halving every year is a pretty clear downwards trend.

The next things to check would be other large countries in Africa -e.g. Egypt, Kenya, South Africa, Ethiopia, Tanzania, Congo and their sample sizes relative to population.

That doesn't give us concrete numbers of users at all, but I think given this is more or less the only data available it is the best we can do.

I think we could probably add country-specific checks to the heuristics issue so will try to get to that and write something up both here and in the other issue.

Assuming ~6 billion people on the internet, 0.05% is 3 million. That's very different from #6's claim of 100 million, and #7 doesn't explain that discrepancy unless we're thinking people are averaging downloading Opera Mini 30 times. https://en.wikipedia.org/wiki/Opera_Mini says that in 2013, it was 300 million active users, though I'm guessing that's worldwide, not just within Africa. It would be nice if we could find some corroboration for either the claim that that has fallen by 100x down to 3 million, or conversely the claim that there's currently 100 million people in Africa using it.

Yes 🌱 Re-evaluate opera mini support Active is the only known change to the current browserl ist.

Opera mini is below 1% (0.04%) on https://caniuse.com/usage-table and it's still in the supported browsers list.

Opera Mobile is above 1%, but it's not in it. More on 🌱 Re-evaluate opera mini support Active .

https://caniuse.com/usage-table has Opera Mini on 0.05% internationally.

All the sign-off have been given, so setting the status to fixed.

All the sign-off have been given, so setting the status to fixed.

Significant parts of feedback have not yet been addressed, and it's still unnecessarily making private APIs public.

@lauriii, not that I know of. Although, 🌱 Re-evaluate opera mini support Active fits with these heuristics.

Do we have a list somewhere on what browser would be supported under the proposed heuristics?

Since the last comment here the core leadership team decided to stop using the Core Ideas project. That means that the current proposal here is outdated and needs to be re-discussed.

On the other hand, there has been very little discussion here, so perhaps the community is managing with the current way of doing things?

Is there interest in outling a more detailed process for feature requests? If there is no interest this may be closed after three months.

Good that the label "Experimental" was added to the database driver description.
I have updated the CR.
Back to RTBC.

Done #152. Added pre/post screenshots drush and GUI.

Testing manually, I can see the new driver showing up at installation time. The CR says differently, so it needs update. Besides, there is no indication that the driver is experimental or hidden - those are 'module' notions, but at the stage of database selection in the installer modules are not yet a thing. So if you select the mysqli driver for installation, the 'experimentality' of the module is a consequence as the driver is included in the mysqli module that is enabled as part of the install process.

I will add explicitly '(experimental)' in the driver string for now. In a follow up, we could add an additional Connection method indicating and reporting the db client in use (it being PDO, mysqli, oci8, sqlite3, etc).

I'm +1 to this because this aligns with the strategy to not compete with contrib. Webform provides clearly a stronger platform to build on top of which most people are choosing as a result. Form building is an important feature, so we may want to consider in future if core should be providing this feature, but it's clear that Contact isn't the right approach to start implementing that.

I'm +1 for moving History to contrib. It is not a key platform feature core needs to be providing and it seems like it could have a better future in contrib.

Creating a database is a nice nitpick, back to RTBC

I updated the links in #41. There are no objections here so RTBC.

Found that mysqli::exec() does not exist while testing manually the GUI installation and database is not yet present.

Re-titling, because pre-selected profiles (pre-filled settings.php, distributions), will still be supported. The only thing we'd be removing here is the form/step for install profile selection.

I'm generally +1 for this, because I like anything that streamlines the installer and gets people up and running more quickly.