Bug 1531289 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I could reproduce this issue in Nightly67 /03.03.2019 ; Beta66.0b11 /02.25.2019 ;   Release65.0.2 /02.25.2019 on Windows 10, Ubuntu 16.04, Osx 10.14. 

IMO, there are two issues here:
1- the blank tab has the URL title of the href anchor; (regression? or intended fix)
2- the tab is not closed after the download selection.

for **1-** Going back to Nightly55, the testcase result is that the _blank is shown, but still is not closed after the download option. Not sure if it's by design or not, the best mozregression could do is to narrow it to [2017-05-23, 2017-05-24] (1 days)- https://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2017-05-23&enddate=2017-05-24 from which bug 1319111 seems most likely candidate. Now that raises the question if this was an intended fix or not.

Honza, could you please take a look to this scenario? I'd rather a confirmation on the expected result of this test case before splitting and triaging this issue further.
I could reproduce this issue in Nightly67 /03.03.2019 ; Beta66.0b11 /02.25.2019 ;   Release65.0.2 /02.25.2019 on Windows 10, Ubuntu 16.04, Osx 10.14. 

IMO, there are two issues here:
1- the blank tab has the URL title of the href anchor; (regression? or intended fix)
2- the tab is not closed after the download selection.

for **1-** Going back to Nightly55, the testcase result is that the _blank is shown, but still is not closed after the download option. Not sure if it's by design or not, the best mozregression could do is to narrow it to [2017-05-23, 2017-05-24] (1 days)- https://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2017-05-23&enddate=2017-05-24 from which bug 1319111 seems most likely candidate. Now that raises the question if this was an intended fix or not.

Honza, could you please take a look to this scenario? I'd rather have a confirmation on the expected result of this test case before splitting and triaging this issue further.

Back to Bug 1531289 Comment 1