Will Howell

@Shane-E the next patch release of the CDK should have a fix for this: https://github.com/angular/material2/pull/12119

It would be easiest (for now) to just support passing a popover instance to not have to duplicate the Input bindings in the service api. Are you thinking something like...

Ahh I see. AFAIK a popover's content won't pollute the DOM until it's opened, but I understand not wanting 100s or 1000s of popover instances hanging around in memory until...

**`SatPopover`** * Inputs * `xPosition` * `yPosition` * `overlapAnchor` * ~`hasBackdrop`~ * ~`backdropClass`~ * Output * ~`opened`~ * ~`closed`~ * Methods * ~`open`~ * ~`close`~ * ~`toggle`~ **`SatPopoverAnchor`** * Inputs...

> How can we track open/close event of sat-popover in component which is shown inside of sat-popover You can inject the `SatPopover` into your child component. Check out this stackblitz...

@sohebcakewalk while you're working on that, maybe this will be helpful: https://stackblitz.com/edit/angular-nbhbg7

Yep this is totally valid and should be a pretty easy fix (just gotta find the time lol). In the mean time, you could look into using css margins for...

Re: #103, that work is already done and the anchoring service is exposed in in https://github.com/ncstate-sat/popover/pull/125. I hate how clunky it is to use though, so I didn't document it...

This may also work better as a globally positioned popover with draggability as an input ```html ``` It would mean that anchors are optional when `global` is specified. Another option...

The `.sat-popover-container` element already has classes applied to it for animation origins https://github.com/ncstate-sat/popover/blob/71069b6e49e141ea3a93b4f0249b2892a0238e88/src/lib/popover/popover.component.ts#L271-L280 Would it be valuable to have those on a different element or some more granularity? @fxck?