Able to reproduce this issue on Windows-10, Ubuntu 14.04 and Mac OS 10.12 using chrome latest stable #57.0.2987.133. By opening the test case file from the original comment, observed it displays "bbb aaa" where as in Firefox it displays as "aaa bbb"

This issue is observed on chrome older version of #35.0.1849.0 as well, Hence marking it as untriaged.

Looks like our bug.

There's a Unicode site you can test:
http://unicode.org/cldr/utility/bidi.jsp?a=%E2%80%AE+bbb+%E2%80%AC%E2%80%AD+%E2%80%AC%E2%80%AE+aaa+%E2%80%AC&p=Auto

says Firefox is correct.

Edge renders the same order as Firefox, but leaves a space at the beginning of the line, which looks incorrect because the spec says to collapse leading/trailing spaces after line break.

NG renders the same order as Firefox, but collapse spaces differently when it needs to collapse across bidi control characters. Hmm, I don't think the spec says this, but when both Edge and Gecko does, we should probably fix the spec.

Thank you for the interesting case.

Test for space collapsing only:
http://jsbin.com/zegida

Edge and Gecko behaves differently here, so probably they reordered spaces differently, but hard to know further from the rendering result.