Post #3098231

@schwa it was ostensibly fixed in beta 3, but sounds like you still see it. I have t had a chance to test removing the workaround on my end yet.