This works for me with ESR 17.0.4 and rev a0215802846726e58edb2f875a06083c0d1b83a3 of the torbrowser repo. But the interesting part is that the test got fixed by rev bd9d79e513c3cbfc7915442599c2224dff147371 accidentally. Or, to put it another way, the test failure was probably indeed a sign of an issue with the patch. That in turn might serve as an argument to get, well, a more professional QA :)
Trac: Resolution: N/Ato worksforme Status: new to closed