(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #6) >> Hmm, Chrome and Safari do the new behavior of us. So, keeping this change must be safer for web-compat. I do not think so. I can not reproduce the issue on Chrome91 Windows10. Simple steps to reproduce: 0. New profile 1. Open web page in [Tab A] (e.g. https://ftp.mozilla.org/pub/firefox/nightly/) 2. Middle-click on a link(e.g. 2004) so that the link opens in a new foreground tab 3. Shift + Middle-click on the other link(e.g. 2010) so that the link opens in a new background tab 4. Back to previous tab[Tab A] Actual Results: Text is unexpectedly selected. -- BUG!! Chrome does not select any text!! --OK Expected Results: Text should not be selected.
Bug 1715603 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #6) >> Hmm, Chrome and Safari do the new behavior of us. So, keeping this change must be safer for web-compat. I do not think so. I can not reproduce the issue on Chrome91 Windows10. Simple steps to reproduce: 0. New profile 1. Open web page in [Tab A] (e.g. https://ftp.mozilla.org/pub/firefox/nightly/) 2. Middle-click on a link(e.g. 2004) so that the link opens in a new background tab 3. Shift + Middle-click on the other link(e.g. 2010) so that the link opens in a new foreground tab 4. Back to previous tab[Tab A] Actual Results: Text is unexpectedly selected. -- BUG!! Chrome does not select any text!! --OK Expected Results: Text should not be selected.