Bug 1914394 Comment 0 Edit History

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

Original comment by
on 
**Found in**
* Latest Nightly 131.0a1

**Affected versions**
* Latest Nightly 131.0a1

**Tested platforms**
* Affected platforms:
* Unaffected platforms: 

**Preconditions**
* Have `browser.navigation.requireUserInteraction` pref set to `true`

**Steps to reproduce**
1. Open `data:text/html,<a href="https://www.mlb.com/tv/g632367?affiliateId=SCORES" target="_blank">Open affected website</a>` in the urlBar
2. Click the Hyperlink
3. Click the Back button

**Expected result**
* The website is opened in a new tab and the back and next buttons are disabled.

**Actual result**
* The mlb website is opened in a new tab but the back button is enabled. Clicking the button will act as if the UserInteraction pref will have the false value.

**Regression range**
* Not a regression since this is reproducible in a very old build (Firefox 79) from when user-interaction was first implemented, bug 1515073.  

**Additional notes**
* I am not entirely sure if this is the correct expected result for this issue but I noticed that on Chrome the back/forward buttons are disabled.
Revision 1 by
on 
**Found in**
* Latest Nightly 131.0a1

**Affected versions**
* Latest Nightly 131.0a1

**Tested platforms**
* Affected platforms:
* Unaffected platforms: 

**Preconditions**
* Have `browser.navigation.requireUserInteraction` pref set to `true`

**Steps to reproduce**
1. Open `data:text/html,<a href="https://www.mlb.com/tv/g632367?affiliateId=SCORES" target="_blank">Open affected website</a>` in the urlBar
2. Click the Hyperlink
3. Click the Back button

**Expected result**
* The website is opened in a new tab and the back and next buttons are disabled.

**Actual result**
* The mlb website is opened in a new tab but the back button is enabled. Clicking the button will act as if the UserInteraction pref will have the false value.

**Regression range**
* Not a regression since this is reproducible in a very old build (Firefox 79) from when user-interaction was first implemented, bug 1515073.  

**Additional notes**
* I am not entirely sure if this is the correct expected result for this issue but I noticed that on Chrome the back/forward buttons are disabled.
* Opening the mlb.com link on its own in a new tab and clicking on the back button will automatically take the user to the about:newtab page.
Revision 2 by
on 
**Found in**
* Latest Nightly 131.0a1

**Affected versions**
* Latest Nightly 131.0a1

**Tested platforms**
* Affected platforms: Windows 11, macOS 13 and Ubuntu 22.04
* Unaffected platforms: 

**Preconditions**
* Have `browser.navigation.requireUserInteraction` pref set to `true`

**Steps to reproduce**
1. Open `data:text/html,<a href="https://www.mlb.com/tv/g632367?affiliateId=SCORES" target="_blank">Open affected website</a>` in the urlBar
2. Click the Hyperlink
3. Click the Back button

**Expected result**
* The website is opened in a new tab and the back and next buttons are disabled.

**Actual result**
* The mlb website is opened in a new tab but the back button is enabled. Clicking the button will act as if the UserInteraction pref will have the false value.

**Regression range**
* Not a regression since this is reproducible in a very old build (Firefox 79) from when user-interaction was first implemented, bug 1515073.  

**Additional notes**
* I am not entirely sure if this is the correct expected result for this issue but I noticed that on Chrome the back/forward buttons are disabled.
* Opening the mlb.com link on its own in a new tab and clicking on the back button will automatically take the user to the about:newtab page.

Back to Bug 1914394 Comment 0