Is it a bug? Or is chrome correctly interpreting the right-to-left override character it sees in the source?
Good point. It is probably the right thing to do technically, since the source view can't rely on parsing the markup. I think I'd prefer such non-printable characters to be simply escaped though.
Are you sure? curling from Terminal, I get the same result.
That's probably because your terminal interprets the RLO character. Should it? I'm not sure.
rxvt-unicode, despite being perfectly able to display unicode characters (hence the name), drops the RLO.