V1 of o-overlay

I'm really not sure I get this.  You'll have a trigger element, an overlay bound to it.  You click the trigger element, the overlay appears.  You click it again, the overlay disappears.  The overlay internally maintains state to know whether it is open or not.  I can't see why you'd have a second instance created on the same trigger unless you did that intentionally, in which case, I see no reason to stop you doing that.