Talk:FAQ/@comment-188.19.55.255-20190408103343/@comment-27190591-20190727190148

Well, it seems you got lucky, because this "bug" was fixed with v35.3.