"perform a non-traverse navigation API navigation" and lack of source browsing context
annevk opened this issue · 1 comments
annevk commented
Since you don't track the source browsing context, doesn't that mean that referrer ends up being set incorrectly? There might also be some problems with per-document policies, such as CSP.
domenic commented
Well, it means referrer will be set as if the browsing context navigated itself. Basically there is no distinction in this API between frames[0].navigation.navigate(...)
and frames[0].eval("navigation.navigate(...)")
, like there is with other APIs. The referrer is always equal to the current URL of the browsing context. That seems OK to me.
See also #110