On 2/24/17, 3:00 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>Having two discussions in one thread is confusing… ;-) > >I guess we could make a custom object, but I’m not sure what the point >is. AIUI, the purpose of IPopUpHost is to support many levels of popups. >Assuming we are right that dialog must be attached to <body>, the >simplest way to handle that is to attach it directly. > >However, I just looked around a bit, and it seems like that’s not true. >It looks like dialog can be attached to pretty much any element. The only >caveat seems to be in the polyfill that it’s supposed to not be in an >element which has a stacking context.[1] > >What I’m not sure about dialog is whether the position can be relative to >an element, or it’s always relative to the whole page. Depending on the >answer to that, it might make sense to allow different IPopUpHosts, or >not. IMO, that's the point of IPopUpHost. It allows various configurations to dictate where to hang the popups. It doesn't have to be body, and in some situations, it might need to be the parent document's body if you are in an IFrame. Regular Flex has a PopUpManager, but really, it was designed for multiple overlapping windows like in MS Windows and was overkill for most applications. In fact, the FlexJS examples don't have a PopUpManager and can still hang one modal dialog at a time somewhere. So, IMO, popup support should also be PAYG and have an abstraction that doesn't assume it is the <body> tag. My 2 cents, -Alex
