What/where is the CSS? With this news, I'd love to update my CSS file to override the mobile configuration then. I thought it wasn't being loaded server side, so this is a welcome change

@Izno so there's progress on this bug? Using Vector 2022 skin, I went to https://en.m.wikipedia.org/wiki/Template:Multinational_unions which is a non-mainspace page and still cannot see it on mobile view. Can you link an example flow that shows what is different? Or am I misunderstanding your response?

@Stevietheman are you using Desktop mode or Mobile mode on phone? I confirmed with my iPhone SE and iPhone 13 on Safari and Chrome browsers; that navigation template doesn't render. For example https://en.m.wikipedia.org/wiki/Foxconn_and_unions, on the other hand, if you call desktop url (without "m") like https://en.wikipedia.org/wiki/Foxconn_and_unions that does render on both mobile phones.

Adding the option for full article editing doesn’t remove the current options for section editing and I imagine performance considerations have reduced over the years. But even so, this is a useful feature. Enabling this would encourage more mobile users to be productive editors. Currently I switch to desktop mode on my phone which is contrary to the whole point of a mobile UI. Adding this as an option underneath edit button seems like simplest solution

That did not work for me unfortunately on https://en.wikipedia.org/wiki/Trader_Joe%27s_unions. I had to switch to source mode (even when loading in safe mode with your link)

Would this be correct way to load a page in safe mode? (Note I am loading it in edit mode already) https://en.wikipedia.org/wiki/Trader_Joe's_unions?veaction=edit?safemode=1

Nope false alert, it's not working again for me. So will try your work around

I am unable to replicate the error anymore, despite not changing anything. I will try some more visual editor edits and try your workaround if anything comes up.

Agreed! I pasted the text from User:Ade56facc and encouraged them to make an account/continue here.

I don't mind if the css is slightly different in mobile...but it's getting a bit ridiculous that a foundation with $100,000,000+ is unable to figure out a solution for English Wikipedia at this point or hire someone who can for a nearly 5 year old exclusionary bug.

This sounds like it has many positives and not so many cons. If someone wants to add a different label that existing behaviour is preserved. One question I have is, if someone wanted to add the "same" label value on a different language, should that trigger a validation error? I can imagine that would potentially disrupt bots who copy labels, but maybe that's not a bad thing if the goal is cleanup.