Yeah, it's something we've been trying to figure out how best to do for a while now. There may be a simpler workaround for this, there's actually a re-write of this extension going on (see this PR) so I have mentioned this there.

There's also a sort-of related issue here.