av9ash/GitBugs huggingface dataset:
Bug: Icons in PDF are rendered with scanlines
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-08-17 13:08:34+00:00
Resolved: 2022-01-05 17:20:45+00:00

**Affected versions**
- Firefox 91.0.1
- Firefox 92.0b4
- Firefox 93.0a1

**Affected platforms**
- Ubuntu 20.04
- macOS 12.0 beta
- Windows 10

**Steps to reproduce**
1. Launch Firefox
2. Access this [PDF Sample](http://www.pdf995.com/samples/pdf.pdf)
3. Scroll down to "Introduction" and zoom in on the blue icon

**Expected result**
- The icon is rendered correctly in PDF

**Actual result**
- The icon is rendered with scanlines

**Regression range**
- Will see for a regression.

**Additional notes**
- The issue can be seen in the attachment.
Bug: Open PDF in newest firefox version displays empty pdf file
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-08-17 13:35:07+00:00
Resolved: 2021-10-23 12:12:56+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0

Steps to reproduce:

Download PDF from a web page
Open PDF in Firefox

Open PDF outside Firefox, older version and other browser


Actual results:

90% of pdf file was empty, except special characters and images

Outside Firefox and in other browser PDF file is displayed correctly and filled in

In older version of Firefox PDF is also displayed correctly, tried this in 90.0.2


Expected results:

PDF file should be displayed with full content when opening in the browser.

Can't attach a file because of privacy reasons.
Bug: Cannot make a screenshoots of bootstrap modal window elements using selenium
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-08-17 14:24:02+00:00
Resolved: 2021-08-26 16:21:26+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.107 Safari/537.36

Steps to reproduce:

Steps su,,a
1. Open https://getbootstrap.com/docs/4.0/components/modal/
2. Scroll to the button "//*[@data-target='#exampleModalLive']"
3. Click the button
4. Make the screenshoot
Pure webdriver js script:
```
const { Builder, By, Key, until } = require('selenium-webdriver');
const fs = require('fs');


(async function example() {
    let driver = await new Builder().forBrowser('firefox').build();
    try {
        await driver.get('https://getbootstrap.com/docs/4.0/components/modal/');
        const button = await driver.findElement(By.xpath(`//*[@data-target='#exampleModalLive']`))

        await driver.executeScript("arguments[0].scrollIntoView(true);", button);
        await new Promise(r => setTimeout(r, 1000));
        await driver.executeScript("window.scrollBy(0, 350);");
        await new Promise(r => setTimeout(r, 3000));
        await driver.executeScript("arguments[0].click();", button);
        await new Promise(r => setTimeout(r, 3000));
        const ss = new Buffer(await driver.takeScreenshot(), 'base64');

        fs.writeFileSync('ss.png', ss);
    } finally {
        await driver.quit();
    }
})();
```
Expected result: the viewport screenshot with the modal window:
image

Actual result: the viewport screenshot without the modal window:




Actual results:

The viewport screenshot don't have the modal window



Expected results:

The viewport screenshot should have the modal window
Bug: Crash in [@ shutdownhang | mozilla::IdlePeriodState::GetIdleDeadlineInternal ]
Status: NEW
Priority: --
Created: 2021-08-17 14:32:31+00:00
Resolved: 2022-01-26 12:50:56+00:00

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Windows 10x64, 21h2 (21354).

Crash report: https://crash-stats.mozilla.org/report/index/01455d2a-591d-4ae3-8a57-86cdb0210817

Unable to identify steps, it was a one-time crash after Refreshing Firefox from the uninstaller and leaving it into the background for a few moments.
Bug: [XFA & AcroForm] The order in which the input fields are being focused/highlighted is incorrect
Status: NEW
Priority: P2
Created: 2021-08-17 14:57:03+00:00
Resolved: 2023-06-02 15:22:04+00:00

**Note**
* When the user loads some specific PDF files and navigates them by keyboard (Tab key), he will notice that the fields are being focused/visually highlighted in the wrong order.

**Affected versions**
* Beta v92.0b4

**Affected platforms**
* all

**Steps to reproduce**
1. Launch browser.
2. Load the attached PDF file.
3. Press the Tab key to focus through the form fields (text fields/radio buttons/checkboxes/combo-boxes/buttons...).

**Expected result**
* The focus should move in an orderly manner, up-down, left-right.
* Then behavior seen in Abobe is the one described above, the most logical one: "Validate" button, "Clear Form" button, "UCI" text field, "I want service in" combo box, "Visa requested" combo box, "*Family name  (as shown on your passport or travel document)" text field, "Given name(s)  (as shown on your passport or travel document)" text field, "Have you ever used any other name (e.g. Nickname, maiden name, alias, etc.) ?" radio buttons set, and so on...

**Actual result**
* The focus is moved from the PDF controls to a radio button (on page 2, sub-section 6, from PASSPORT section), then to an "Email address" text field (on page 2, sub-section 6, from CONTACT INFORMATION section, then (presumably) focuses the "Validate" and "Clear Form" buttons from the top of the document, only then finally focusing the first field of the document (1. UCI).

**Regression range**
* Not a recent regression, but it is important to notice that a more confusing behavior can be seen in Release v91.0 since a visual focus was even more lacking (XFA disable under pref in this channel).

**Additional notes**
* I have set this bug's severity as S2, because it could be a very complicated and confusing process for keyboard users. Please lower it if it is believed to be too high.
* [access] keyword set because it's an interest of keyboard users.
Bug: [XFA] Buttons have no focus indicator when navigating by keyboard
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2021-08-17 15:50:42+00:00
Resolved: 2023-06-02 15:22:04+00:00

**Note**
* When the user loads some specific PDF files and navigates them by keyboard (Tab key), he will notice that the buttons are not visually highlighted, although focused.

**Affected versions**
* Beta v92.0b4

**Affected platforms**
* all

**Steps to reproduce**
1. Launch browser.
2. Load the attached PDF file.
3. Press the Tab key to focus through the form fields to reach some buttons. (the only way to notice that the buttons are being highlighted is to observe that the page jumps up and the buttons are the first thing in view.

**Expected result**
* When focusing on the buttons, there should be a clear visual representation of them.

**Actual result**
* When focus reaches the "Validate" or "Clear Form" buttons, no clear visual representation is seen.
* The focus is moved from the PDF controls to a radio button (on page 2, sub-section 6, from PASSPORT section), then to an "Email address" text field (on page 2, sub-section 6, from CONTACT INFORMATION section, then (presumably) focuses the "Validate" and "Clear Form" buttons from the top of the document, only then finally focusing the first field of the document (1. UCI)...

**Regression range**
* Not a recent regression, but it is important to notice that a more confusing behavior can be seen in Release v91.0 since a visual highlight was even more lacking (XFA disabled under pref in this channel).

**Additional notes**
* I have set this bug's severity as S4 because the functionality of these buttons is not even supported yet. Dynamic elements of XFA forms are covered in meta bug 1717661 (not yet supported). 
* I've set it to block bug 1706133 because the highlight is a matter of navigation.
* [access] keyword set because it's an interest of keyboard users. Removed it if believed to be correct.
Bug: Intermittent [Tier2] browser/components/urlbar/tests/browser/browser_searchMode_setURI.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-08-18 03:14:06+00:00
Resolved: 2021-09-14 17:06:45+00:00

**Filed by:** nbeleuzu [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=348770999&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/QhqhoHC6RD2Y8JELgmZbrQ/runs/0/artifacts/public/logs/live_backing.log

---
```
[task 2021-08-18T02:09:33.121Z] 02:09:33     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchMode_setURI.js | Expected placeholder l10n when search mode is inactive - {"args":{"name":"Google"},"id":"urlbar-placeholder-with-name"} deepEqual {"id":"urlbar-placeholder-with-name","args":{"name":"Google"}} - 
[task 2021-08-18T02:09:33.121Z] 02:09:33     INFO - Leaving test bound setURI
[task 2021-08-18T02:09:33.122Z] 02:09:33     INFO - Buffered messages finished
[task 2021-08-18T02:09:33.122Z] 02:09:33     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_searchMode_setURI.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2021-08-18T02:09:33.123Z] 02:09:33     INFO - GECKO(1554) | MEMORY STAT | vsize 20976276MB | residentFast 1841MB
[task 2021-08-18T02:09:33.123Z] 02:09:33     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_searchMode_setURI.js | took 97655ms
```
Bug: jar:file/// protocol URLs no longer work from the address bar
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2021-08-18 07:54:27+00:00
Resolved: 2021-09-16 16:46:17+00:00

STR:
1. Try to visit `jar:file///PATH/omni.ja!/` from the address bar (replace `PATH` with Firefox install folder).

Expected:

Address bar action is "Visit" and opens the file directory for the `omni.ja` archive.

Actual:

Address bar action is "Search with" and sends URL to search engine.

It still searches even with `keyword.enabled = false`.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=28e04a08d2e42d3579b28b36becda67d945d6abe&tochange=1a7ab6a8f1adbbecf5dead68a7fa3a92c2fd958c

Regressed by Bug 1580881.
Bug: Show bookmark toolbar on a new tab unexpected behavior
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-08-18 08:16:00+00:00
Resolved: 2021-08-18 08:22:33+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

Go to about:preferences#home
Set new tabs > blank page (instead of Firefox Home)
Change bookmark toolbar to show only on new tab.




Actual results:

Open a new tab, the bookmark toolbar does not show even though "Only show on new tab" option is selected.


Expected results:

The bookmark toolbar should appear on a new tab, when using the blank page option.
Bug: [XFA] Data saved with Firefox won't display in Adobe Reader
Status: RESOLVED
Priority: P1
Resolution: WORKSFORME
Created: 2021-08-18 12:19:23+00:00
Resolved: 2021-11-04 18:00:30+00:00

**Note**
* When the user opens a specific PDF file in Firefox, inputs some data, saves it and opens it in Adobe Reader, he will notice that the data input using the browser is NOT displayed in Adobe Reader.

**Affected versions**
* Beta v92.0b5

**Affected platforms**
* all

**Steps to reproduce**
1. Launch browser.
2. Flip "pdfjs.enableXfa" to true.
3. Load the attached PDF file.
4. Input some data in any field.
5. Save the document (CTRL+S)
6. Open the document in Adobe Reader

**Expected result**
* The data input using the browser is displayed in Adobe Reader.

**Actual result**
* The data input using the browser is NOT displayed in Adobe Reader.

**Regression range**
* Not a regression.

**Additional Information:**
* The input data is properly displayed if opened in Firefox again.
* I do not know whether this should block bug 1706133. Remove the block if not necessary.
Bug: Saving some webpages fails when using strict tracking protection
Status: NEW
Priority: P3
Created: 2021-08-18 13:42:56+00:00
Resolved: 2023-03-06 19:00:25+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

Try to save webpage:
https://www.bd2020.com/jd/26885.htm

Right click -> Save Page As... (or Ctrl + S).


Actual results:

Fails to download webpage


Expected results:

Download webpage.
Bug: Intermittent browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | insertNodeInWindow should have placed new XUL widget in correct place in DOM according to placements - Got "customizableui-special-spring2", expected "test-wid
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2021-08-18 14:42:03+00:00
Resolved: 2022-08-12 20:33:39+00:00

**Filed by:** abutkovits [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=348802047&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/RxNzB9rvSbG1aNzCSgkgxA/runs/0/artifacts/public/logs/live_backing.log

---
```
[task 2021-08-18T12:51:13.275Z] 12:51:13     INFO - TEST-PASS | browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | New XUL widget should be placed inside overflow of toolbar - 
[task 2021-08-18T12:51:13.275Z] 12:51:13     INFO - TEST-PASS | browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | insertNodeInWindow should have placed new XUL widget in correct place in DOM according to placements - 
[task 2021-08-18T12:51:13.276Z] 12:51:13     INFO - TEST-PASS | browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | insertNodeInWindow should have placed new XUL widget in correct place in DOM according to placements - 
[task 2021-08-18T12:51:13.276Z] 12:51:13     INFO - Leaving test bound 
[task 2021-08-18T12:51:13.277Z] 12:51:13     INFO - Entering test bound 
[task 2021-08-18T12:51:13.277Z] 12:51:13     INFO - TEST-PASS | browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | New XUL widget should be placed inside overflow of toolbar - 
[task 2021-08-18T12:51:13.277Z] 12:51:13     INFO - Buffered messages finished
[task 2021-08-18T12:51:13.278Z] 12:51:13     INFO - TEST-UNEXPECTED-FAIL | browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | insertNodeInWindow should have placed new XUL widget in correct place in DOM according to placements - Got "customizableui-special-spring2", expected "test-widget-for-insertNodeInWindow-placements-1"
[task 2021-08-18T12:51:13.278Z] 12:51:13     INFO - Stack trace:
[task 2021-08-18T12:51:13.278Z] 12:51:13     INFO - chrome://mochikit/content/browser-test.js:test_is:1364
[task 2021-08-18T12:51:13.278Z] 12:51:13     INFO - chrome://mochitests/content/browser/browser/components/customizableui/test/browser_976792_insertNodeInWindow.js:null:245
[task 2021-08-18T12:51:13.279Z] 12:51:13     INFO - TEST-PASS | browser/components/customizableui/test/browser_976792_insertNodeInWindow.js | insertNodeInWindow should have placed new XUL widget in correct place in DOM according to placements - 
[task 2021-08-18T12:51:13.279Z] 12:51:13     INFO - GECKO(1573) | [Child 1578: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 0 (1173c5400) [pid = 1578] [serial = 21] [outer = 0] [url = http://example.com/]
[task 2021-08-18T12:51:13.280Z] 12:51:13     INFO - Leaving test bound 
```
Bug: [XFA] An extra empty page is shown in print preview
Status: NEW
Priority: P3
Created: 2021-08-18 14:51:17+00:00
Resolved: 2022-01-28 14:41:51+00:00

**Note**
* When the user loads a specific PDF file and prints it, he will notice that the browser's printed version adds an extra empty page to the bottom.

**Affected versions**
* Nightly v92.0b5

**Affected platforms**
* all

**Steps to reproduce**
1. Launch browser.
2. Flip "pdfjs.enableXfa" to true.
3. Load the attached PDF file.
4. Notice the number of pages it has; Then Ctrl + P
5. Scroll to the bottom of the print preview.

**Expected result**
* The print preview has the same number of pages as the document itself. It has no empty pages at the end.

**Actual result**
* The print preview has an extra page as the document itself. An empty page is observed at the bottom.

**Regression range**
* This is a regression of:
Bug 1724461 - Update pdf.js to version 2.11.91 r=pdfjs-reviewers,calixte
Differential Revision: https://phabricator.services.mozilla.com/D122023

**Additional information**
* Appears to be a general issue.
Bug: [XFA] (De)Selections of checkboxes are incorrectly saved
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-08-18 15:22:20+00:00
Resolved: 2021-11-18 15:04:16+00:00

**Note**
* When the user loads a specific PDF file in Adobe Reader, selects some specific checkbox then unchecks it, and then saves it and reopens it, he will notice that the checkbox shows it's checked when in fact it should be unchecked.

**Affected versions**
* Nightly v92.0b5

**Affected platforms**
* all

**Steps to reproduce**
1. Launch browser.
2. Flip "pdfjs.enableXfa" to true.
3. Load http://static.anaf.ro/static/10/Anaf/Declaratii_R/AplicatiiDec/D100_710_XML_1220_260321.pdf
4. Check the checkboxes:
[ ] Declaraţie depusă după anularea rezervei verificării ulterioare
[ ] Declaraţie depusă potrivit art.90 alin.(4) din Legea nr.207/2015 privind Codul de Procedură fiscală
5. Uncheck them!
5. Save the PDF file.
6. Reopen it.

**Expected result**
* The checkboxes should be unchecked.

**Actual result**
* The checkboxes are checked.

**Regression range**
* Not a regression.

**Additional information**
* This issue does not occur on all checkboxes, but on specific ones.
Bug: Unable to login
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-08-18 15:38:47+00:00
Resolved: 2021-08-19 12:08:41+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Safari/605.1.15

Steps to reproduce:

I tried to make access


Actual results:

arrived at the moment of entering the security code, opening the mailbox the security code does not arrive in time before it expires.


Expected results:

That the security code doesn't expire after 5 minutes since it takes much longer to receive the email.
Bug: Error when closing all tabs
Status: NEW
Priority: --
Created: 2021-08-18 18:41:49+00:00
Resolved: 2021-08-18 23:32:20+00:00

Firefox fail at gBrowser._insertTabAtIndex when trying to close all selected tabs.

Tested on Firefox 93.0a1 2021-08-17

Steps to reproduce:
1. new clean profile.
2. set browser.tabs.closeWindowWithLastTab to false.
3. set browser.tabs.insertAfterCurrent to true.
4. open more than one tab, select all tabs.
5. close all tabs using close x tabs from tab context menu.

Result:
```
Failed to create tab
    addTab chrome://browser/content/tabbrowser.js:2813
    addTrustedTab chrome://browser/content/tabbrowser.js:2528
    _beginRemoveTab chrome://browser/content/tabbrowser.js:3799
    removeTab chrome://browser/content/tabbrowser.js:3591
    removeTabs chrome://browser/content/tabbrowser.js:3524
    removeMultiSelectedTabs chrome://browser/content/tabbrowser.js:3407
    closeContextTabs chrome://browser/content/tabbrowser.js:7131
    oncommand chrome://browser/content/browser.xhtml:1

can't access property "_tPos", this.selectedTabs[(this.selectedTabs.length - 1)] is undefined
    _insertTabAtIndex chrome://browser/content/tabbrowser.js:3235
    addTab chrome://browser/content/tabbrowser.js:2701
    addTrustedTab chrome://browser/content/tabbrowser.js:2528
    _beginRemoveTab chrome://browser/content/tabbrowser.js:3799
    removeTab chrome://browser/content/tabbrowser.js:3591
    removeTabs chrome://browser/content/tabbrowser.js:3524
    removeMultiSelectedTabs chrome://browser/content/tabbrowser.js:3407
    closeContextTabs chrome://browser/content/tabbrowser.js:7131
    oncommand chrome://browser/content/browser.xhtml:1
```
Bug: ugly google calendar display in firefox 91 on Big Sur
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-08-18 22:02:18+00:00
Resolved: 2021-08-20 20:00:57+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

rebooted and opened my calendar after upgrading to Big Sur and firefox 91. 


Actual results:

I tried to attach 2 files, one each from firefox and safari, but bugzilla did not allow that. So... I attached the crappy display of calendar from firefox.

I've been using firefox forever. If this is not fixed, I will definitely toss it off my systems and tell all my students to do the same.


Expected results:

firefox should look much more like the safari display.
Bug: "Connection is not secure" icon shown for file:// protocol URLs
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-08-19 00:12:14+00:00
Resolved: 2021-08-20 07:56:16+00:00

clicked hyperlink for PDF file; firefox asked what to do with it - i said open in firefox. i noticed the "Connection is not secure" icon (crossed-out padlock) is getting displayed in the location bar, which doesn't make sense given that there's no connection at all and the file is being loaded locally.
Bug: Internal PDF Reader is always used when called from a local HTML file
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2021-08-19 06:46:26+00:00
Resolved: 2022-01-24 11:17:44+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

I have some local HTML file which contain links to local PDF files. E.g
file:///home/frank/mypdffiles.html
and inside mypdffiles.html
<a href="mypdffile.pdf">my PDF file</a>


Actual results:

Since Firefox 91 only the internal PDF viewer is used to open these PDF files. The application settings are completely ignored. I can select "Always ask" or "Open with mypdfviewer", but this setting is ignored.
For remote files HTML pages, the behavior is as expected. But not for local HTML files. 


Expected results:

The application settings should also be valid for local HTML files, not only for remote web pages.
Bug: [Linux ] Localized address bar chiclet can be totally replaced by ellipses
Status: NEW
Priority: P3
Created: 2021-08-19 08:22:02+00:00
Resolved: 2021-08-20 23:41:21+00:00

+++ This bug was initially created as a clone of Bug #1724212 +++

**Affected versions**
* Nightly 92.0a1 2021-08-18

**Affected platforms**
* Ubuntu 18.04 64-bit

**Steps to reproduce**
1. Download a Firefox localized build (eg: ta, pl)
2. Open a certificate error page (eg: https://wrong.host.badssl.com/)
3. Check the address bar chiclet
4. Narrow browser width to min and verify the address bar chiclet
5. Check if a tooltip is available when the chiclet is not entirely visible

**Expected result**
* As described in Figma, the chiclet text should always be visible, no matter the window size

**Actual result**
* On narrow windows, text can be totally replaced by ellipses 


**Regression range**
* Not a regression, leftover bug from Bug 1724212.
Bug: Block incognito mode not working with selenium
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2021-08-19 09:25:19+00:00
Resolved: 2021-09-10 12:40:22+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36

Steps to reproduce:

1. Disable incognito mode on windows 10 with registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\DisablePrivateBrowsing
2. Try to open Firefox in incognito mode with Selenium
```
user_profile = webdriver.FirefoxProfile('C:/Users/jazz/AppData/Roaming/Mozilla/Firefox/Profiles/3ykp28o8.default-release') # current user profile
 user_profile.set_preference("browser.privatebrowsing.autostart", True)
driver =  webdriver.Firefox(user_profile)
```
3. Firefox opens in incognito mode

I am unable to open the Firefox in incognito mode manually, so incognito mode is definitely disabled


Actual results:

I could open Firefox in incognito mode with Selenium, even though incognito mode was disabled


Expected results:

Expected to not be able to open Firefox in incognito mode