Does umbraco v14 * backoffice* work on mobile for you? I was surprised to discover that it doesn't and I need some sanity check 😄 I used google chrome mobile device emulator... can anyone confirm this is really the case?

Wow, yeah that's not great https://cdn.discordapp.com/attachments/1285553433138696203/1285558079135420457/Screenshot_20240917_130639_Chrome.jpg?ex=66eab4c2&is=66e96342&hm=3dc9d059e151b3f4c40a37c89a3fd711a514e39a66702e4662c97cdbb6d14f93& https://cdn.discordapp.com/attachments/1285553433138696203/1285558079416700960/Screenshot_20240917_130628_Chrome.jpg?ex=66eab4c2&is=66e96342&hm=a69a80c1e2266c35a9570ec353575eb2e0fd998840c693458dc96cf0d39972d3&

@Kaspar Boel Kjeldsen thanks for checking out - appreciate it

I'd create that as a bug on github if I were you 🙂

We don't support the backoffice on small resolutions and/or touch officially, but happy to receive contributions towards better support in this area

@Jacob Overgaard you do in 13 though - the tree structure behaves very differently between 13 and 14

I agree, the experience was better in V13

I see 🙂 Contributions are prolly the way to go then but I will say it's not small issue. The menu down right breaks on mobile just to be clear. It's not harder to use. It's unusable, and that will come as a shocker for some who are used to be able to make minor changes/check things on the go

Might be mistaken.. but don't I remember a big fanfare about umbraco 8? backoffice supporting mobile devices.. would be a shame if we've lost it along the way 😦

@Mike Chambers umbraco 8 also has a mobile response tree menu unlike Umbraco 14, so it's currently possible (with a bit of patience) to edit content/settings on Umbraco from at least version 8 up to and including 13.

Spoke to Umbraco support, and they are aware of the issue, but not sure it was on some issue list. I've reported bug here: https://github.com/umbraco/Umbraco-CMS/issues/17083

Just FYI: we have never focused on it, the answer has always been a variation of this: https://github.com/umbraco/Umbraco-CMS/issues/10921

@Sebastiaan you've might not focused on it, but it was usable :/ It honestly feels a bit hot potato-y to be like it's never been our focus, so it doesn't matter that it doesn't work now. Whether it got in through contributions or through HQ development isn't really the main point as I see it. It's been expected behavior for quite some time for a lot of us who have used it.

Really, the only answer I have for you is: it's never been officially supported, it worked by luck and some community contributions. We'd LOVE some PRs to make the current situation better, but a mobile backoffice is not on our roadmap.

Might be a good hacktober candidate ?

As much as I would like it to happen the complexity and flexibility of the Umbraco back office would be an incredible amount of work to make usable on small screens.

@Dean Leigh again.. It was usable though... I use it occasionally on v8 and v13

To be fair it is/was kind of usable on v13 and earlier. What I meant was there is a lot of work to get it working for larger screens as a priority.

I'm not here to throw any stones or complain as I understand this has not been a priority and things take time. But I want to inform about our (a digital agency's) perspective on this. This is such an important issue to the level where we have to move away from Umbraco on upcoming projects for our several of our clients that expect at least a usable experience, if not perfect. In certain mobile browsers you can use a "simulate desktop" mode sort of, and on Brave on Android for example this actually makes it usable when you zoom in/out. On Chrome on iOS this mode weirdly enough does not help - you're still stuck in a zoomed in view with things out of bound and not scrollable.

FYI This is a setting you can change in most mobile browsers, "force enable zoom"

Is this something different from "simulate desktop" (Android Brave), or "Request Desktop Website" (iOS)? Some accessibility thing maybe? (trying to get my iOS friend to try it)

ah I don't have iOS, it's in acessibility on Chrome on Android. I would say though, I don't think we don't need to force the zoom level at all on mobile, that's something that should be easily fixed with a PR to the

viewport

meta tag.

The problem on iOS (tried with two colleagues now) is that even if you request the desktop version, you are unable to zoom out, unable to "see everything" so to say, and unable to scroll/pan around to the things that are hidden in view. Basically if you emulate a mobile phone in devtools you can immediately see how you're "locked in". And on Android it works great to request desktop site and see things properly but for some reason iOS (both Safari and Chrome) does not act in the same way. Would the solution with viewport be to add a

minimum-scale

? Perhaps we could try this locally for an iOS user.

Okay, I don't understand what Safari is doing there, but if there's a fix, then should be fine to put in I'd think.. v15 says

<meta name="viewport" content="width=device-width, initial-scale=1.0" />

The one v15 site we have currently is for a client and I can't really share video from it, but if we get around to it I can share more clearly what the problem is. I don't know yet what iOS is having trouble with so no idea if it can be fixed via viewport tag yet.

think it's that initial scale maybe, I can't zoom out enough on android either to see a Save button (for example) when making a new doctype