Hi, I'm working on the WebDriver BiDi implementation in Firefox, and I'm looking at the WebDriver BiDi download started triggered from the HTML spec (step 5.4.4 of https://html.spec.whatwg.org/#attempt-to-populate-the-history-entry's-document). I have a couple of questions around this (spawned from https://github.com/w3c/webdriver-bidi/issues/980).

First, do I understand correctly that this is not triggered when users click on a link with a download attribute? (which goes through https://html.spec.whatwg.org/#downloading-hyperlinks).
Then if that's correct, I would like to change this so that we also trigger the BiDi hook in case of a download attribute. But then I'm not sure there would be a navigation id relevant to send to BiDi in this case?

(I can also file an issue on GitHub if preferable to discuss about this)

annevk: do you remember details of this comment? https://github.com/mozilla/standards-positions/issues/466#issuecomment-745120322

Is the no-referrer-based redaction not sufficient?

zcorpan: ah

This is even further complicated when an embedded site is navigated as the site being navigated to would never know about its parent (other than that one exists).

is a case where we start exposing more information and also more strongly conveys that referrer policy now has this dual purpose. I think that's probably all okay though and it's relatively straightforward to follow.