We're pushing more things to the frontend to make render caching work. We need to make sure proxy browsers are not impacted negatively.

We got Mobile first pretty much done but fact is, a lot of the mobile traffic is through proxy browsers in non-EU and non-US countries.
ppk on Nigeria browsers
ppk on India browsers

Browsers we should support:
Opera mini
Xpress
UC

Comments

nod_’s picture

nod_
Primary language French
Location Lille
commented

Looks like #2118703: Introduce #post_render_cache callback to allow for personalization without breaking the render cache will make sure that is the case.

nod_’s picture

nod_
Primary language French
Location Lille
commented
Issue tags: +mobile

tag

catch’s picture

catch
he/him
Primary language English
commented

That issue is in, it doesn't remove the js we're using in core, but it makes it possible to swap that out for a PHP-only solution if necessary. Does that leave this as critical? I'm not sure it needs to be critical unless there's an actual known incompatibility.

nod_’s picture

nod_
Primary language French
Location Lille
commented

Haven't done extensive testing yet. The problem is that usually *some* JS is supported but not everything, if proxy browsers were using the bare no-js version there wouldn't be a problem but I'm worried about things like contextual links and the toolbar degrades in them.

nod_’s picture

nod_
Primary language French
Location Lille
commented

Quick things showed with testing on Opera proxy.

  • Toolbar is in no-js mode
  • Contextual links do not appear
  • CKEditor is unusable, can't focus in the textarea (can still change text format as expected though)
  • Back to site link doesn't show up
  • Responsive tables do no work completely (can't "Show all columns")
  • Tabledrag doesn't initialize
  • Dropbutton on the node/edit form (other works)
  • Machine name (does show up after the validation error though)

What does work:

  • Dropbutton
  • Changing a text format
catch’s picture

catch
he/him
Primary language English
commented
Priority: Critical » Major
Issue summary: View changes

I'm going to bump this down from critical.

If you disagree, then I think we need an issue to add these browsers to https://drupal.org/node/61509 before we make bugs in them release blocking.

cilefen’s picture

cilefen commented

Is running those browsers in device emulators good enough or are there cloud services that are better for testing?

If a test environment is not difficult to implement, we could have novice contributors perform manual testing and keep a running list of issues in the summary of this issue.

It looks like Nokia Xpress has been replaced with Opera Mini as the default browser on that platform.

droplet’s picture

droplet commented
Related issues: +#1030090: Document our browser support list 
Is running those browsers in device emulators good enough or are there cloud services that are better for testing?

I can tell even iPad sometimes we have to test it in a REAL Device. Also, you may not able to figure out it works perfect or lagging from the super slow android emulators.

I'm working for IE6 ~ 8 bugs a long time and see that's almost ZERO testers. I can't imagine what will happening in these kind of proxy-like browsers. We should not telling the world Drupal supports X but end up with nothing :)

this is a case with a patch for 1 year but no IE reviewers: #2182265: Drupal.t() placeholder substitution doesn't always work correctly (backport part of the Javascript file translation fixes from Drupal 8)

Opera Mini =/= Opera Mobile

It's very complicated: (search `Mini`)
https://stats.wikimedia.org/archive/squid_reports/2015-02/SquidReportCli...

Actually based on my own exp, almost all of my NON-tech friends also have a second mobile browsers on their smartphone. That said, they may use Opera Mini as default browsers, but they will switch to another one if they find something do not working correctly.

That will be cool if we can invite someone living in that area to share their insider's views

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)
Related issues: +#2390621: [policy, no patch] Update Drupal's browser support policy

Do we still need this now that #2390621: [policy, no patch] Update Drupal's browser support policy landed? Opera Mini is now officially supported.

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented
Status: Postponed (maintainer needs more info) » Active

We did some very high-level testing as part of #2390621: [policy, no patch] Update Drupal's browser support policy. I think it would be valuable to do a more detailed review and file issues for any bugs we find.

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented
Version: 8.6.x-dev » 8.8.x-dev
wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Component: base system » browser system

👍

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

heddn’s picture

heddn
Primary language English
Location Illinois
commented
Issue tags: -JavaScript +JavaScript

Stumbled upon this when looking at https://caniuse.com/srcset. Which got me to thinking, how fully supported are these browsers on mobile? Something as common as srcset isn't supported on Opera Mini. How standards compliant is it? Should it be dropped?

heddn’s picture

heddn
Primary language English
Location Illinois
commented
Title: Make sure D8 works with mobile proxy browsers » Make sure Drupal 10 works with mobile proxy browsers

Re-titling since D8 is no longer supported. And 10.x will be released best case in 6 months.

heddn’s picture

heddn
Primary language English
Location Illinois
commented

Of note from #3192234-139: Apply width and height attributes to allow responsive image tag use loading="lazy":

Just noting, as per conversation just now with @heddn, that Opera Mini is widely used in Africa on mobile devices.

According to https://gs.statcounter.com/browser-market-share/mobile/africa , it's got a 12% market share on mobile devices.

Which pretty much debunks my question in #24. Opera mini is used in certain regions of the world.

droplet’s picture

droplet commented

Opera Mini (a.k.a proxy browsers) is officially dropped. The reason is simple: Drupal has never supported it from DAY ONE.
(In other words: this is NOT dropped but report the truth [after 5 years or 12 years...))

And above stat, what OPERA means is a black hole. (not just above stats, almost everywhere or even Opera official site is unclear)

I think to support them is almost to support IE6/7. We were never able to go back.
Even to support non-Chromium Edge is a bit difficult now IMO.

heddn’s picture

heddn
Primary language English
Location Illinois
commented
Related issues: +#3202818: Remove untrue declaration of Opera Mini (in reverse proxy mode) support from Drupal 9.3

Also linking in #3202818: Remove untrue declaration of Opera Mini (in reverse proxy mode) support from Drupal 9.3, which clarifies some points around opera mini.

nod_’s picture

nod_
Primary language French
Location Lille
commented
Status: Active » Closed (won't fix)

Our frontend code didn't change much since 8 years ago, and devices got faster. I don't think this is relevant anymore.