In T229875#5396278, @Jdlrobson wrote:

We shouldn't add <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, shrink-to-fit=no"> to Vector. When Monobook did that it annoyed a lot of people and I wouldn't advise it as it seems many users use Vector on their mobile devices exactly because they don't want a responsive layout.

Do you have a link and/or do you remember where this annoyance was voiced?

In T229875#5409585, @phuedx wrote:

In T229875#5396278, @Jdlrobson wrote:

We shouldn't add <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1, shrink-to-fit=no"> to Vector. When Monobook did that it annoyed a lot of people and I wouldn't advise it as it seems many users use Vector on their mobile devices exactly because they don't want a responsive layout.

Do you have a link and/or do you remember where this annoyance was voiced?

https://de.wikipedia.org/w/index.php?title=Wikipedia:Fragen_zur_Wikipedia&oldid=178125403#Merkw%C3%BCrdige_Seitendarstellung

In T229875#5396278, @Jdlrobson wrote:

Varnish determines when to show or not show the mobile website and that's purely based on user agent and this is out of the teams expertise and will require syncing with ops.

Yes and no. The mobile_redirect subroutine is fairly simple (see https://github.com/wikimedia/puppet/blob/dd8b6a8339bdc6b389c794b0e7ad5f4338d30194/modules/varnish/templates/text-frontend.inc.vcl.erb#L27).

However, the user agent iPadOS sends is not a mobile [one], so if iPadOS wants to be recognised as desktop that's going to be impossible to change.

This. Ignoring minor version numbers, that UA is the same as mine (Safari 12.1.2 on macOS Mojave 10.14.6). Unless we want to redirect ALL such UAs to the mobile site, then UA sniffing won't work here.

@ovasileva okay to redirect Safari desktop to mdot?

CC @DStrine @mepps @Ejegg @BBlack

In T229875#5432239, @dr0ptp4kt wrote:

@ovasileva okay to redirect Safari desktop to mdot?

CC @DStrine @mepps @Ejegg @BBlack

@dr0ptp4kt - I would be more comfortable with making a request to Apple on redirecting iPad OS to Safari mobile. I think redirecting to the mobile domain on Safari desktop would have negative consequences to editors using Safari, which we would like to avoid if possible.

Okay, let me look into this.

In T229875#5432239, @dr0ptp4kt wrote:

@ovasileva okay to redirect Safari desktop to mdot?

CC @DStrine @mepps @Ejegg @BBlack

@dr0ptp4kt Thanks!!! As far as I can tell, regardless of how this is resolved, there are no significant short- or medium-term implications for CentralNotice or Fundraising.

(The only possible immediate impact, I think, is in the statistics for banner impressions on iPads vs. desktop, but there's nothing we could do about that. And, I guess, banners not showing up properly on a broken layout, if the issue isn't solved and a lot of users experience breakage...)

In the longer term, we do need to think about responsive design for banners, and how CentralNotice and Advancement banners (like the little reminders that follow you around as you scroll) will fit in with the desktop refresh.

In the longer term, we do need to think about responsive design for banners, and how CentralNotice and Advancement banners (like the little reminders that follow you around as you scroll) will fit in with the desktop refresh.

+1 on this. We should discuss once we're a bit further along on the project.

@cchen copying you in for visibility. iPad iOS 13 is a desktop UA, in case that's useful info in other contexts.

Adding a note. in iPadOS 14 the behavior appears to be different from what is described in the description. The content appears to work well in the desktop layout (skinny viewport limitations withstanding). While Apple has not released updated adoption rates since iPadOS 14 was released in September, this report indicates a 70% adoption rate of iPadOS 14.