As is officially stated and discussed on Super User, Chrome Canary is a very fast-forward beta test channel.
Canary build: Canary builds are the bleeding edge. Released daily, this build has not been tested or used, it's released as soon as it's built. Because there's no guarantee that it will even run in some cases, it uses it's own profile and settings, and can be run side by side another Chrome channel. By default, it also reports crashes and usage statistics to Google (you can disable this on the download page).
It contains untested feature and tweaks. It's not even known whether they will stay in any later stable releases. Any bug on a web page, including Stack Exchange, may be caused by Chrome Canary. As I've tested by myself, this bug does not exist in Chrome Stable 57.0.2987.133 for Windows.
On mobile using desktop view, it does, but why do you think a perfect layout from a desktop site on mobile is necessary? As per animuson's comment, that page renders correctly in a desktop browser and in the mobile view, so there's nothing to fix. As previously stated, Stack Exchange don't officially support mobile browsers on the desktop view of the site. That's why there is a separate desktop view and mobile view. Using the desktop view on mobile, you're bound to find oddities as mobile devices use very different methods of rendering.