Indeed, my original request was a naive approach, which is why I
suggested in comment #1 identifying what in chromium’s implementation we
want to replicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The other thing from that chromium code is that the closing order should
be different. In the case you describe of having opened B, C and D
background tabs. Closing D should not focus A (which created it) but
instead focus C.
--
You received this bug notification because you are a member of
I looked into chromium’s implementation, and it’s a bit more complex
than what I described in the description. Details are in
TabStripModelOrderController::DetermineNewSelectedIndex(…)¹.
I think it would be worth identifying what in chromium’s implementation we want
to replicate.
One thing that
** Branch linked: lp:~fboucault/webbrowser-
app/switch_to_parent_tab_on_close
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664990
Title:
Restore focus on parent tab when closing child tab
To
** Changed in: webbrowser-app (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664990
Title:
Restore focus on parent tab when closing child tab
To