Hmm, which errors?

For https://office.wikimedia.org/w/index.php?oldid=228334&veaction=edit&debug=true&action=edit in Firefox 59 I get:

• unreachable code after return statement in index.php:876:8 coming from https://office.wikimedia.org/w/index.php?title=MediaWiki:LAPI.js&action=raw&ctype=text/javascript (I have no idea what's calling that though)
• Mapping(s) missing from citoid-template-type-map.json: case in ve.ui.Citoid.init.js:61:3 coming from https://office.wikimedia.org/w/extensions/Citoid/modules/ve.ui.Citoid.init.js?69ff8

I tried this in Chrome, and didn't produce any errors. (I did see the Mapping(s) missing from citoid-template-type-map.json: case one, but that's a warning.) Firefox got the unreachable code warnings, too. No auto-switching observed in either case.

Working ok for me.

In T190056#4061688, @Aklapper wrote:

• Mapping(s) missing from citoid-template-type-map.json: case in ve.ui.Citoid.init.js:61:3 coming from https://office.wikimedia.org/w/extensions/Citoid/modules/ve.ui.Citoid.init.js?69ff8

T190071

I was having this problem in Safari. I didn't grab a screenshot, so I can't tell you which error message it was. @Elitre, how are things working for you on office.wiki this week?

I don't think I ever had an auto-switch issue. OTOH I haven't used VE there for over a week since it's giving me a few headaches. I will make an effort to document my problems here if people are willing to take a look at those.

It works this morning. Maybe a temporary server problem? (All I recall about the error messages is that they took a very long time to appear and that the information in them amounted to "didn't work".)

That sounds plausibly like the "didn't get a decent answer from restbase / parsoid" case, yeah. Which would likely look like this:

That is plausible.

I've found the visual editor on officewiki to be fairly unreliable; sometimes it works fine, and other times it shows this error. I primarily use Chrome, for what it's worth.

As an anecdote I think things are worse when section editing?

This was almost certainly the same issue as T187951, and I can't reproduce this any more, so I'm merging these together.