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_’s picture

Issue tags: +mobile

tag

catch’s picture

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

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

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

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

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

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.