WICG / document-picture-in-picture

https://wicg.github.io/document-picture-in-picture/
Other
55 stars 9 forks source link

Be more clear about what owns what #8

Closed steimelchrome closed 1 year ago

steimelchrome commented 1 year ago

Migrated issue from https://github.com/steimelchrome/steimelchrome.github.io/issues/6

From domenic@:

" It seems like maybe browsing contexts own DocumentPictureInPictureSessions? If so that should be declared somewhere. But it's a surprising choice; do you really want a PiP session to last if the user navigates from https://example.com/ to https://other.example/? (A browsing context is like a browser tab.)

In general, you want to declare up-front what types of objects own what other types of objects, and add definitions for that ownership. Then, when you access an object, you need to traverse the ownership graph. An example from https://wicg.github.io/navigation-api/ is how it declares each Window owns a navigation API (an instance of Navigation), and each Navigation owns an entry list. "

domenic commented 1 year ago

I think this is pretty much fixed now, except #59.

steimelchrome commented 1 year ago

Okay I'll close this one then