That's exactly what I did (albeit using Stylish extension), but it would be great tp have a proper fix on this (or any traction at all).

In T228962#8260459, @Aklapper wrote:

Might be T282385#7073151 ?

This seems getting worse and started to affect other wikis, like Japanese Wikipedia:

Ah that sounds good. Thanks.

I don't think the search results will show what we want.

Seems to have been updated just now.

Lately I noticed Google even start to show mobile link for zh.wiki.

Which comment there is #4438037? The anchor doesn't work.

Any updates on this?

In T246314#6025304, @Xiplus wrote:

In T246314#6025302, @fireattack wrote:

https://zh.wikipedia.org/zh-cn/User:Fireattack/%E6%B2%99%E7%9B%92

It's broken on my device. See also: https://archive.vn/DmlT6.

Why it isn't broken in my sandbox (case 2)?

Yeah, feel free to close it.

Thanks for taking time to reply, really appreciate it.

More details about "Reverting to platform default font would not be the best experience in many cases" would be appreciated.

In T234703#5553694, @Volker_E wrote:

sans-serif provides suboptimal reading experience

It seems to be changed in T175877.

It returns content-type: image/png here (using both curl and browser).

It is fixed here for https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/Shin-marunouchi.Building-2007-01.jpg/100px-Shin-marunouchi.Building-2007-01.jpg

Sorry, that must be a typo. Meant to add "MediaWiki-File-management" (like T26763).

I think my question is, are these shortcuts supposed to work?

If by CodeMirror you mean syntax highlighting, yeah, the bug (shortcuts don't work) is there regardless; just that Syntax Highlighting will give some weird visuals, like it's trying..

Oh Thanks for the detailed reply!

But neither Microsoft's Office online (I tried Excel Online) or Google Docs (tried Spreadsheet) have this IME problem.

Also I did a quick test on cs.wiki (with an Android phone). It can redirect to correct mobile views of other language version of Wikipedia just fine (no idea how the reporter there has successful rate of only 10%).

I didn't get it. What's the difference between T156578 and this one? Isn't it exactly the same bug? Why reopen that and keep this (firstly-reported) one as low & stalled?

Sorry I didn't specify, I use Chrome 56.

In T155928#2960089, @Liuxinyu970226 wrote:

In T155928#2960073, @fireattack wrote:

In T155928#2960069, @Liuxinyu970226 wrote:

In T155928#2959929, @Esanders wrote:

Pretty sure this was reported before - but can't find it.

Either way - as we use keydown to change modes, I think it will be hard to not affect the IME. Maybe we could use compsitionstart, but I'm sure there are IME's that won't play nicely, right @dchan?

Looks like T49436 for Sogou?

I saw that one, but it doesn't specify which part is glitching.

In my experience everything is fine until I start to edit tables

Therefore, every CJK IMEs are affected?

In T155928#2960069, @Liuxinyu970226 wrote:

In T155928#2959929, @Esanders wrote:

Pretty sure this was reported before - but can't find it.

Either way - as we use keydown to change modes, I think it will be hard to not affect the IME. Maybe we could use compsitionstart, but I'm sure there are IME's that won't play nicely, right @dchan?

Looks like T49436 for Sogou?

Not sure what's the technology behind Google Docs/Spreadsheet, seems to work fine with IME there

A showcase GIF

Also reported at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_151#Media_player_has_weird_buffering_problem_when_replaying

Any fix on this? It still exists and is quite annoying.

@Aklapper: Despite that ticket is highly related to this one (I actually mentioned this bug somehow there years ago), I think they're not the same problem as all. That's why I deliberately opened a brand new ticket to bring the attention to developers actually.

So I think this bug should be "Canonical URL should be /wiki/ links, but somehow Google doesn't honor it".

I don't know why the title of this page reads "Canonical URL should include language variant" (because it shouldn't). But anyway, I'm here to report the exact weired behavior mentioned above: