Page MenuHomePhabricator

On analytics.wikimedia.org, Safari on iOS ignores collapsed tabs interaction; stats dashboard is poorly navigable on Safari on iOS and Chrome on Android
Closed, InvalidPublic

Description

I was testing the website https://analytics.wikimedia.org via latest versions of Safari and Chrome on iPhone 5s (iOS 12.4.8) and iPadOS 14.1 (latest version of supported iPads). Seems that, on iOS version of Safari, the website's UI would not respond to touch screens' interactions with collapsed tabs. Nonetheless, I can still tap on the "Contact" tab.

On the other hand, I tested the site on Chrome. The site can respond to my tapping on the tab but most likely while using Chrome.

The problems are not limited to just the site's main page. While using Chrome on iOS and Android smartphones, the stats dashboard (especially the browser stats) is poorly navigable. Text scrambles, and the inner window of the graph shrank, while the rest of the dashboard webpage. I can give you smartphone screenshots, but I'm uncertain whether that's necessary. Test the site out on Chrome or Safari via any smartphone, and I hope you'll understand my point.

Using an iPad, the site is easier to navigate, but the site issues are similar while using Safari. On Chrome via iPad, the site still works and is easier to navigate. However, the dashboard doesn't respond to my touches/tapping on graphs while trying to analyze rates of browser and OS usages. If an iPad's version is iPadOS 13.4 or later, you should connect either a compatible mouse or separate trackpad to the device since I don't know whether the site works with a mouse. I know that the site is barely responsive to touchscreens.

Event Timeline

Aklapper renamed this task from analytics.wikimedia.org incompatible on iOS and Android to On analytics.wikimedia.org, Safari on iOS ignores collapsed tabs interaction; stats dashboard is poorly navigable on Safari on iOS and Chrome on Android.Oct 21 2020, 10:49 AM

Hi @gh87, thanks for taking the time to report this! This ticket seems to mix several unrelated things together and hence is not actionable. It would be good to split this into dedicated tickets with only one issue per one ticket, and clear steps to reproduce. See https://www.mediawiki.org/wiki/How_to_report_a_bug - thanks!

Splitting into separate tasks: T266122, T266132, T266142