BroadcastChannel should work for opaque origins |
||||
Issue descriptionAs discussed in https://github.com/whatwg/html/issues/1319#issuecomment-263966028, the current behavior of throwing when creating a BroadcastChannel in an opaque origin context is not correct. We should fix this. This will likely involve some renderer side coordination to keep messages destined for the same thread in the renderer (as we don't have a cross-thread/cross-process way to identify opaque origins). That still won't be enough to also enable communication with same-opaque-origin workers for example, but at least it's closer to the spec'ed behavior.
,
Feb 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 16 2018
This is definitely still a thing for interop, although not very high priority.
,
Aug 1
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Jan 18 2017