For some profiles, allowescapesequence works and for other it does not. Adding BR so I can remember to figure out why this happens for some profiles.
Could this behaviour have had the same root cause as bug 469511? Allowescapesequence not applying to new sessions/tabs can make the setting feel very inconsistent and that behaviour was introduced with MR !211.