1877430 - Consider consuming the user activation when clicking a link that would open a new tab or an external application

Status: NEW

(Core :: DOM: Core & HTML, task)

Description

[Edgar Chen [:edgar]]

Attachment: testcase.html

We consume the user activation on window.open, even though spec only checks for user activation without consuming it. Chrome also consumes the user activation, there is a spec issue to clarify this behavior. <a target=_blank> uses the same choosing a navigable steps, so it makes sense to have a consistent behavior with window.open. The link that would open external application is similar to <a target=_blank> in some sense, so we might also want to consume the user activation like Chrome does.

Comment 1

[Oliver Medhurst [:canadahonk]]

I presume we aren't worrying about potentially breaking sites as Chromium already has this behavior?

Comment 2

[Oliver Medhurst [:canadahonk]]

I believe we already sometimes do this for external protocols here, but only in some situations. I'll add 2 blocking bugs for each situation.

Comment 3

[BugBot (nomail) [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.