Comment 8 for bug 1611287

Whether it's hackish or not, it is a step we're taking to work around an obstacle snappy throws up but provides no mechanisms to deal with.

I think we're all taking roughly the same approaches, and that's encouraging that people are unlikely to get this wrong if we can't fix it. But it does make for a rather un-DRY experience that is a bit jarring.

I would support adding some sort of mechanism to make these sorts of operations first-class and consistent.