Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,515,026 | 13,820,507 |
Created attachment 9032119
rec of the issue.gif
[Affected versions]:
- Firefox 65.0b4 and above
[Affected Platforms]:
- All Windows
- All Linux
- All Mac
[Prerequisites]:
- Have the latest Firefox Nightly build installed.
- Have the "Browser Console" opened.
- Have a Firefox profile with the following prefs in the "about:config" page:
- "browser.newtabpage.activity-stream.asrouterExperimentEnabled" with "true" value;
- "browser.ping-centre.log" set to "true".
[Steps to reproduce]:
1. Open the browser with the profile from prerequisites.
2. Navigate to "about:config#asrouter" page.
3. Scroll down to the "NEWSLETTER_TEST_1" section and click the "Show" button.
4. Focus the "Browser Console" and clear all the output from it.
5. Go back to the "AS Router" page and click the snippet's "Continue" button.
6. Focus the "Browser Console" and observe the displayed pings.
[Expected result]:
- A specific ping is displayed in the "Browser Console".
[Actual result]:
- No pings are displayed.
[Additional Notes]:
- This issue is also reproducible with the "FXA_SNIPPET_TEST_1" and the "SNIPPETS_SEND_TO_DEVICE_TEST" snippets.
- According to the "QA plan for ASR Snippets" doc (https://goo.gl/KCLbkM), a specific ping should be displayed in the "Browser Console".
- Attached a screen recording of the issue.
|
|
1,515,030 | 13,820,551 |
Created attachment 9032122
Screen Shot 2018-12-18 at 2.23.03 PM.png
Build: 15.0(13375)
Device: iPhone 7
iOS: 12.1
Steps to reproduce:
1. Clean install Firefox
2. Log in to FxA
Actual results:
- Top Sites are incorrectly displayed.
|
|
1,515,088 | 13,820,946 |
From Bug 1481518 comment 17.
The problem here appears to be that it does some part of the DLL loading on a new thread.
The chromium sandbox sets an impersonation token on the main thread of the child process with more rights, so that it can do general start-up things like load DLLs. This is reverted early in the process when we call TargetServicesBase::LowerToken.
I can see the child process spinning up a new thread and calling NtQueryAttributesFile on mozglue.dll, which fails because that thread has the more restricted token.
The brokering won't work either because we haven't called TargetServicesBase::Init and it's possibly too early in the process start-up anyway.
|
|
1,515,129 | 13,821,336 |
Created attachment 9032215
Screenshot of message telling me to get Chrome.
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.0 Safari/605.1.15 Epiphany/605.1.15
Steps to reproduce:
Load your Facebook wall.
Select "Live Video".
Instead of working, Facebook pops up a message that says that Live Video now requires the latest version of Google Chrome, and it refuses to let you use it in Firefox.
Actual results:
Firefox is blocked from using Live Video.
Expected results:
Live Video should have opened my webcam and allowed me to go live after granting permissions.
In fact, Live Video does work in Firefox. When I overrode my user agent for Facebook websites with an extension and told it I was using Chrome 71 on Linux, Live Video popped up and worked fine.
|
|
1,515,153 | 13,821,472 |
Based on bug 1511104 comment 10, it is unlikely we can get utm params passed through our web properties, but we could strip the "utm" part of the param name and make it work that way. However, the attribution code needs to accept either to make that work.
|
|
1,515,379 | 13,823,386 |
This is causing us to report a wildly high. This field used to be a type that had a default initializer.
|
|
1,446,762 | 13,136,377 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180317220121
Steps to reproduce:
Once opened Nightly window on 1080p monitor, and moved into 1440p monitor, Skin doesn't adjust, and just have this greenish spot.
https://i.imgur.com/vovfekq.png
Actual results:
https://i.imgur.com/vovfekq.png
Expected results:
Adjust skin width correctly.
did not have this problem with Firefox quantum.
|
|
1,446,913 | 13,138,999 |
On Google Chrome and Firefox 59, middle-click on a link opens a tab next to the current tab and notifies only a "tabs.onCreated" event with correct "index". On the other hand, Firefox 60 beta and Nightly 61 notify "tabs.onCreated" with wrong "index" and extra "tabs.onMoved" event is also notified.
Steps to reproduce:
1. Start Firefox.
2. Go to "about:config" and set "browser.tabs.insertRelatedAfterCurrent"
to "true".
3. Install any addon which has "tabs" permission.
Assume that you install Tab Center Redux:
https://addons.mozilla.org/ja/firefox/addon/tab-center-redux/.
4. Open remote debugger for the addon.
5. Choose "Console" tab and run following script:
------------
chrome.tabs.onCreated.addListener(tab=>
console.log(`tabs.onCreated, index=${tab.index}`));
chrome.tabs.onMoved.addListener((id, info)=>
console.log(`tabs.onMoved, from ${info.fromIndex} to ${info.toIndex}`));
------------
6. Prepare two tabs A(index=0) and B(index=1) with something webpage.
Assume that you open "https://www.mozilla.org/en-US/firefox/".
7. Select the tab A and middle-click on any link in the page.
Assume that you click the link "Get Involved".
Actual result:
The console says:
> tabs.onCreated, index=2
> tabs.onMoved, from 2 to 1
Expected result:
The console says:
> tabs.onCreated, index=1
|
|
1,446,948 | 13,139,300 |
[Affected versions]:
- Firefox 61.0a1 (20180318220108)
- Firefox 60.0b4 (20180315232954)
[Affected platforms]:
- Win 7 64-bit
- Mac OS X 10.13.2
[Steps to reproduce]:
1.Set extensions.langpacks.signatures.required to false.
2.Install some unsigned langpacks.
3.Observe “Languages” from about:addons.
[Expected results]:
- The langpacks are displayed.
[Actual results]:
- The langpacks are not displayed but you can see in the extensions folder from the profile, that they are installed.
|
|
1,446,963 | 13,139,416 |
Created attachment 8960145
Screen Shot 2018-03-19 at 15.30.35.png
Build: 11.0 (9713)
Device: iPad Air 2
iOS: 11.2.5
Steps to reproduce:
1. Open a new tab
2. Go to google.com
3. Tap on the "Back" button to go to homepage
Actual results:
- Google.com title and favicon are displayed.
|
|
1,447,052 | 13,140,112 |
Created attachment 8960235
Flashing.mov
Nightly 61.0a1 (2018-03-19) (64-Bit)
macOS 10.12.6
1.) Use a the official Dark Theme or a darker Theme
2.) Create a new Window via CMD-N
Actual: The whole Toolbar+Tabstrip flickers white
Expected: No flicker.
This is a regression: Works fine with Firefox Stable.
|
|
1,447,056 | 13,140,124 |
Created attachment 8960238
Preferences.png
I was trying to view the internal meeting today and it wouldn't work. I suspected that maybe this was related to bad cookie, so in nightly I went into the cookie manager, attempt to delete the air.mozilla.org cookie, and then upon saving that change, I got into a weird unrecoverable state.
Symptoms:
1.) UI prompt with no ability to accept the change
2.) Cannot close the existing tab
3.) Cannot draw focus of any other other tab
To fix the issue, I needed to quite nightly and restart it.
|
|
1,447,080 | 13,140,383 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36
Steps to reproduce:
Download and run these files:
Known malware: https://demo.smartscreen.msft.net/download/known/knownmalicious.exe
Unknown program: https://demo.smartscreen.msft.net/download/unknown/freevideo.exe
Offline: Any of the above with internet on the machine off
More details about the issue:
In the next Windows Release (Redstone 4), Windows Defender SmartScreen will honor the SEE_MASK_FLAG_NO_UI flag. This flag is passed through shellexecute when a user runs an executable, or other supported file, through the firefox download manager. Edge/Windows Explorer do not pass this flag and are unaffected.
There are three problematic scenarios
1. Known malware - Blocked silently: We will not show any SmartScreen UI for these types of files, but the user will have no opportunity to override the block through firefox. The user will not have any indication that executing the file did anything.
2. Unknowns - The file is unknown to our service. This is a large number of files and all will be allowed. There is a chance for polymorphic malware to be bucketed here.
3. Offline - User is unable to contact smartscreen. Always allowed.
When SEE_MASK_FLAG_NO_UI is not set, all 3 cases will result in a block experience for the user.
Actual results:
Files are not run. They are silently blocked
Expected results:
Files are not run. They are blocked by SmartScreen.
|
|
1,447,193 | 13,141,538 |
Created attachment 8960415
table.html
Build ID : 20180319100039
User Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
It happens from time to time.
When Scroll down or up, the new visible area would not be drawn.
Mouse hover over the area do NOT help.
Mouse clicking on the page will paint correctly.
Once happened the problem, it is somewhat easier to reproduce on the problematic tab.
Reproducible: It happens from time to time
Steps To Reproduce(not 100%):
1. Bookmark the following page in the folder
about:home
the attached page
the attached page
the attached page
the attached page
the attached page
the attached page
2. Restart browser and maximize
3. Middle click on the folder
Now, you can see
[tab1] about:home
[tab2] about:home
[tab3] the attached page
[tab4] the attached page
[tab5] the attached page
[tab6] the attached page
[tab7] the attached page
[tab8] the attached page
4. For each tab, scroll up / down with mouse wheel or autoscroll
5. Close a tab and try Step4
6. Undo close and try Step4
I think it is difficult to find a regression window...
[NOTE]
* Setting layout.display-list.retain = false does NOT fix.
* Disabled HWA also does NOT fix.
|
|
1,447,226 | 13,141,743 |
Created attachment 8960455
OhNoes.png
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20100101
Steps to reproduce:
This may be related to bug 1430391
STR (UI)
- In Developer (60, tested) or Nightly (not tested), go to Options>Privacy & Security>Firefox* Data Collection and Use
- There are two checkboxes (labeled 1 and 1b in the attached image). These are collect data (1) and shield studies (1b)
- In the UI, if you check or uncheck send technical data (1), it auto checks or unchecks studies (1b)
- Note: **from the UI**, you can allow data collected and disallow studies, but NOT vice versa
[1 - data] governs datareporting.healthreport.uploadEnabled
[1b - studdies] governs app.shield.optoutstudies.enabled
STR (about:config)
- in about: config set datareporting.healthreport.uploadEnabled=>false and app.shield.optoutstudies.enabled=>true
- look at the UI, it has achieved a state that contradicts itself?
Note: I do not know if this is just cosmetic or affects the sending of shield data
Actual results:
See attachment
Expected results:
When datareporting.healthreport.uploadEnabled=false then app.shield.optoutstudies.enabled needs to also be toggled to false
|
|
1,447,679 | 13,145,622 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180315233128
Steps to reproduce:
1. Open dev tool
2. Go to network monitor
3. Go to any sites
4. Select any row and details panel will be displayed
5. Click the "Raw headers" button
6. Compare the ordering of the raw and processed response headers
Actual results:
The raw headers field sorts the response headers in alphabetical order just like the processed headers. This doesn't happen in Firefox 58.
Example:
HTTP/2.0 200 OK
content-encoding: gzip
content-security-policy: frame-ancestors 'none'
content-type: text/html; charset=utf-8
date: Wed, 21 Mar 2018 14:38:16 GMT
referrer-policy: strict-origin-when-cross-origin
server: nginx
strict-transport-security: max-age=63072000; includeSubDomains
X-Firefox-Spdy: h2
Expected results:
The raw headers field preserve the original ordering of the response headers
Example:
HTTP/2.0 200 OK
server: nginx
date: Wed, 21 Mar 2018 14:37:36 GMT
content-encoding: gzip
content-type: text/html; charset=utf-8
content-security-policy: frame-ancestors 'none'
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=63072000; includeSubDomains
X-Firefox-Spdy: h2
|
|
1,447,723 | 13,146,113 |
Page action command fails in an extension that uses page action pattern matching and a key command with _execute_page_action.
manifest:
"page_action": {
"default_popup": "page.html",
"show_matches": ["<all_urls>"],
"browser_style": true
},
"commands": {
"_execute_page_action": {
"suggested_key": { "default": "Alt+Shift+3" }
}
}
This is a regression starting in fx59 from bug 1437178.
|
|
1,447,752 | 13,146,309 |
Created attachment 8961057
Screen Shot 2018-03-20 at 17.16.09.png
The fill colour for the search bar should be #FFFFFF. Right now it's the same colour as the New Tab background colour (#f9f9fa) so it looks disabled.
|
|
1,447,796 | 13,146,856 |
Page action command fails to close the page action panel when run twice. With the below, the first key command should open the panel, the second should close it. The pageaction code uses its own panel, so the browserPageAction stuff cannot control this. ext-pageAction simply always assumes it needs to be opened.
manifest:
"page_action": {
"default_popup": "page.html",
"show_matches": ["<all_urls>"],
"browser_style": true
},
"commands": {
"_execute_page_action": {
"suggested_key": { "default": "Alt+Shift+3" }
}
}
I initially thought this might be a regression from bug 1395387, but it is not, and there are no tests built around this. It may have simply always been.
Patch is on top of bug 1447723.
|
|
1,447,871 | 13,147,401 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180319175655
Steps to reproduce:
Load various youtube videos in the same tab. The more videos the worse the ram usage is and more severe the delays. May need to load around 5-15 videos before the issue is clear.
I recorded a video showing how to create the problem from scratch using new profile:
https://youtu.be/a_mzc5DDUz0
I also recorded a performance profile in that same video, here it is:
https://perfht.ml/2GNizma
Actual results:
Eventually you will notice any webpage within that tab will have intermittent moments of unresponsiveness. Actions such as hovering over the video seek bar, highlighting text, typing into text fields or trying to adjust the volume using the volume slider can be delayed for a few seconds. Scrolling the page seems smooth and unaffected. Firefox UI also does not seem affected so typing and highlighting text in the address bar is smooth. Also new tabs and windows are not affected and closing the problem tab seems to fix/reset the problem.
Expected results:
There should not have been any performance impact.
|
|
1,447,977 | 13,148,194 |
Created attachment 8961346
geckodriver.log
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
Steps to reproduce:
Execute this sample using Selenium Java binding:
driver.get("http://todomvc.com/examples/scalajs-react/#/");
driver.executeScript("return document.getElementsByTagName('input')");
Actual results:
JavascriptException: TypeError: cyclic object value
See attached trace level log for more details.
|
|
1,447,982 | 13,148,236 |
STR
1 Go to https://jsfiddle.net/jib1/n7bmkjnf/
2 Accept the permission prompt
3 Uncheck the "echoCancellation" checkbox
Expected:
Checkbox remains unchecked
Actual:
Checkbox immediately re-checked
Looks like a regression from bug 1440040 when I replaced SetLastPrefs() with ApplySettings().
|
|
1,448,132 | 13,149,606 |
Created attachment 8961519
PermissionPromptOff.png
STRs:
1. Open browser.
2. Open https://jsfiddle.net/jib1/r60bzmrs/ in a new (second) tab.
3. Don't answer the prompt.
4. Instead, drag this tab into its own window.
Expected result:
Permission prompt remains open, hanging off the camera icon in the url bar.
Actual result:
Permission prompt remains open, but severely misplaced, to the right and down.
See attached image.
Regression range:
3:07.35 INFO: Narrowed inbound regression window from [7cc75e6d, 84ea4220] (4 builds) to [c842abb7, 84ea4220] (2 builds) (~1 steps left)
3:07.35 INFO: No more inbound revisions, bisection finished.
3:07.35 INFO: Last good revision: c842abb7cfbf39e0c1cfb9a1f3a1d6415cd10744
3:07.35 INFO: First bad revision: 84ea422093dd615bd191a3e579ed299d96c802f1
3:07.35 INFO: Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c842abb7cfbf39e0c1cfb9a1f3a1d6415cd10744&tochange=84ea422093dd615bd191a3e579ed299d96c802f1
My guess is bug 1193394.
|
|
1,448,146 | 13,149,742 |
This is annoying.
Reproducible : always
Steps To Reproduce:
1. Disable HWA
2. Close browser
3. Launch Nightly
Actual Results:
black window without UI is opened at start up. And then switch to normal color.
Expected Results:
No black window at start up.
Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e21a2a57d05dfe3c5ff8ba71131127fa781ffdd0&tochange=f026ead5dbfce9d6530429ac568ecc5544cc9b3b
Regressed by: f026ead5dbfc Florian Quèze — Bug 1447719 - Set browser.startup.blankWindow to true on Windows and Linux, r=mconley.
And I confirmed that setting browser.startup.blankWindow = false fixed the problem
@:florian,
Your patch seems to cause the regression. Can you look into this?
|
|
1,448,200 | 13,150,357 |
If I run Firefox Nightly in a completely clean environment on one of my Fedora 27 64-bit x86 machines, go to a web page with a multi-line textarea (one where spelling checking is or would be active), hover my mouse over the textarea without clicking on it, and then right-click to bring up the context menu, the first time I do this the context menu does not come up and the browser console will report:
TypeError: realSpellChecker is null
(In the current Firefox Nightly this is reported as being from InlineSpellCheckerContent.jsm line '54:5'.)
If I right click a second time, the context menu appears. If I click in the textarea to select it before I right click to bring up the context menu, everything is fine; this includes clicking in it and starting to type text. In all cases spell checking appears to be active if I actually enter text.
My clean environment for this test is created with:
export HOME=/tmp/randombit
mkdir $HOME
cd $HOME
[run appropriate firefox version]
Now that I do more testing, this doesn't seem exclusive to Nightly. I can make it happen in the current Firefox Beta (60.0b5), and also in the current release version (Firefox 59.0.1). Some Internet searches for this specific message suggests that it was happening to some people at least as far back as last summer.
|
|
1,448,288 | 13,151,111 |
This is a follow up for bug 1311177
See also this comment:
https://bugzilla.mozilla.org/show_bug.cgi?id=1311177#c38
In Chrome, the object returned from getHAR is a HAR "log" (http://www.softwareishard.com/blog/har-12-spec/#log), so you could do something like:
function gotHar(har) {
document.querySelector("#har").textContent = `Har: ${har.version}`;
console.log(har);
}
document.querySelector("#gethar").addEventListener("click", () => {
chrome.devtools.network.getHAR(gotHar);
});
Firefox should behave the same.
Honza
|
|
1,448,374 | 13,151,803 |
Created attachment 8961823
test-extension.zip (WRONG VERSION, USE THE UPDATED VERSION)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180315233128
Steps to reproduce:
It may sound strange, but I swear this is all true.
I've created a GitHub Gist for this issue here: https://gist.github.com/AlexanderOMara/6a9a5ac610078a70b49353b41b2dbda2
I've also created a video of the issue here: https://www.youtube.com/watch?v=VNKD40UspzM
----
Loading a `.javascript` file from a WebExtension's [web_accessible_resources](https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/web_accessible_resources) somehow causes problems with the macOS file associations, most notable so with TextMate 2.
Tested On:
- macOS 10.13.3 (native and in a clean VM)
- Firefox 59.0.1 (Stable)
- Firefox 60.0b5 (Developer Edition)
- Several previous Firefox versions
Reproduce Instructions:
1. Download this Gist if you have not already.
2. Install [TextMate 2 RC 8](https://github.com/textmate/textmate/releases/download/v2.0-rc.8/TextMate_2.0-rc.8.tbz) (exact version probably does not matter).
3. In Finder navigate to the Gist, select `file.js` and `file.txt`, click File > Get Info, and set all of them to open with TextMate, making sure to click "Change All" for each one.
4. Make sure TextMate is not running, then open Firefox 59.0.1 (exact version probably does not matter), ideally with a new profile.
5. Go to `about:debugging`, click "Load Temporary Add-On" and open the `manifest.json` file in this Gist.
6. Verify in Finder that TextMate is still the default editor for `.js`, and `.txt` files.
7. Go to a page that loads `google-analytics.com/analytics.js`, like [this minimal one](https://cdn.rawgit.com/AlexanderOMara/485d4a794eb861dc36745a85503edea2/raw/523fe64b31abb33fb844bd39b771dd51b7f7d3f8/index.html).
8. In Finder, select `file.js`, and `file.txt` again and click File > Get Info and see that it has changed (you can also try opening them to confirm it has changed).
9. Open TextMate.
10. Repeat step 8 to see it has actually changed back.
11. Reload the page from step 7 to see it change again.
Notes:
- You can simply refresh the page to see the issue repeat.
- You can edit `background.js` to load `war-test.js` instead of `war-test.javascript` and see the issue no longer happens.
- Other extensions do not seem to cause the problem, it seems something is special about the `.javascript` extension.
- If the `moz-extension://` URL is known and added to the DOM, it is possible to trigger the issue without a `onBeforeRequest` redirect.
- Requests to `.javascript` files outside of `web_accessible_resources` does not cause an issue.
- Current versions of uBlock Origin (1.15.12+, since [this commit](https://github.com/gorhill/uBlock/commit/17930cc778c20e11fd4c760d710e8ba619aab666)) also causes this issue.
Actual results:
When the `war-test.javascript` file is loaded, Firefox somehow changes the file associations on some files. This specifically happens on `.javascript` files, and not `.js` files or any other extension I've tried.
Expected results:
Nothing should have happened, Firefox should not have touched the users file associations.
|
|
1,448,473 | 13,152,599 |
Bug 1408121 made that the dark theme also applies to the menus in Firefox. But there is an usability regression, at least on macOS: the hover style is missing on menu items. It still works for the default theme and for the light theme.
|
|
1,448,599 | 13,153,614 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180316021353
Steps to reproduce:
1) Create a basic WebExtension with the following permission in "manifest.json":
"permissions": [ "webRequest", "<all_urls>" ]
and in the Javascript some basic logging on various webrequest events:
function makeLogger(label) {
return function (evt) {
console.log(label + " : " + evt.url + " - " + evt.statusCode)
}
}
browser.webRequest.onHeadersReceived.addListener(
makeLogger("Header"),
{urls: ["<all_urls>"]}
)
browser.webRequest.onResponseStarted.addListener(makeLogger("RespStart"),
{urls: ["<all_urls>"]}
)
browser.webRequest.onCompleted.addListener(makeLogger("RespCompl"),
{urls: ["<all_urls>"]}
)
2) Open a URL that performs a redirection. In my case, if I open "google.com", I get a redirection to an URL starting with https://www.google.co.jp/
Actual results:
The HTTP request for original request (ex: google.com) is logged (with code 302), but the target URL of the redirection (ex: google.co.jp) is not logged at all. The images referenced by the target of the redirection are properly logged.
Note that if the final URL is manually requested, then it is properly logged.
Expected results:
According to the documentation [1], an event should be generated at each stage of the diagram. The "onHeadersReceived" callback should be called for the 302, then again for the target page, then the "onResponseStarted" callback should be invoke, and at last the one for "onCompleted".
[1] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest
|
|
1,448,674 | 13,154,111 |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171024165158
Steps to reproduce:
A WebExtension contains an option page which communicates with the background script as below :
- option page script call browser.runtime.connect
- background script listen to browser.runtime.onConnect
1. Open the option page of extension.
2. Detach the tab containing option page from main window.
3. Attach the tab to the main window.
Actual results:
When the option page is attached to the window i.e. when the event tabs.onAttached is fired, the event Port.onDisconnect is fired too and it is not possible to communicate with the background script anymore.
Until Firefox 59 : Port.onDisconnect was not fired with tabs.onAttached.
Firefox Beta 60 : UNCONFIRMED.
Firefox Nightly 61 : Port.onDisconnect is fired with tabs.onAttached.
Expected results:
Port.onDisconnect should not fire with tabs.onAttached such as in previous version of Firefox.
|
|
1,448,817 | 13,155,367 |
Created attachment 8962286
testcase.html
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180325220121
Steps to reproduce:
With WebRender enabled in Firefox Nightly, elements with certain combinations of the rotate()-transform and border-radius render incorrectly. I have extracted the attached testcase based on code that I am currently working on.
Actual results:
When the elements have been rotated beyond a certain degree, their colours render slightly brighter than intended and surrounding box-shadows seem to leak through them. The issue does not appear when border-radius is removed.
|
|
1,448,830 | 13,155,485 |
[Affected versions]:
- Esr 52.7.3
- Firefox 59.0.1
- Beta 60.0b6
- Nightly 61.0a1
[Affected platforms]:
- Windows 10 x64
- macOS 10.12, macOS 10.13
- Ubuntu 16.04
[Steps to reproduce]:
1. https://www.bing.com/images/
2. Perform a search
3. Click on an image
4. Hover over the image and click on the magnifying glass / "Search within this image" button
5. Scroll through the results.
[Expected result]:
- The scroll goes at a normal speed.
[Actual result]:
- The scroll has a slower speed. It doesn't seem to lag. The action is performed smoothly, it's just that it seems to navigate a short distance.
[Regression range]:
- I don't think this is a regression. I can reproduce the issue even on Nightly 20.0a1.
|
|
1,448,867 | 13,155,735 |
SSIA
Str
1. Enable dark theme
2. Open Hamburger Menu
3. Mouse hover over menu item
|
|
1,448,896 | 13,155,968 |
Created attachment 8962369
aboutsupport.txt
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180325220121
Steps to reproduce:
1. Create new profile on nightly win10x64 intel iGPU
2. enable WR. Restart
3. Go to https://lab.hakim.se/linjer/#diagonal
Actual results:
page flicker
Expected results:
not so
|
|
1,443,850 | 13,111,566 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
Steps to reproduce:
Test page:
https://fetch-progress.anthum.com/test/sw-response-with-url-fragments/
URLs containing hash/fragment values (e.g. "image.png#value") prevent Service Workers from responding correctly when new Response() constructor is used. This bug does not occur in FF 58 and was introduced in FF 59.
History of bug discovery:
https://github.com/AnthumChris/fetch-progress-indicators/issues/9
Actual results:
Images with URL fragment values do not display when intercepted by Service Worker
Expected results:
Images with URL fragment values should display.
|
|
1,443,937 | 13,112,385 |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20100101
Actual results:
There's no easy way to stop autoscrolling in the latest nightly, left click interacts with the content below the cursor, middle click repositions the autoscroller at the place that was clicked, right clicking creates a context menu and interacts with the page.
Expected results:
Middle clicking anywhere while the autoscroller is showing should stop autoscrolling, not reposition and continue autoscrolling.
|
|
1,444,086 | 13,114,033 |
Created attachment 8957159
crash.html (minimised testcase)
The following testcase crashes the latest ASAN build of Firefox 60.0a1 (SourceStamp=a6a32fb286fa9e5d5f6d5b3b77423ab6b96c9502).
crash.html:
<script>
o935=document.createElementNS('http://www.w3.org/1999/xhtml','canvas');
o935.getContext('webgl2',{depth: true,stencil: true,antialias: true,premultipliedAlpha: false,preserveDrawingBuffer: true,failIfMajorPerformanceCaveat: false,});
o935.setAttribute('height','3');
o2819=o935.getContext('webgl2',{stencil: false,preserveDrawingBuffer: true,failIfMajorPerformanceCaveat: true,});
o3250=o2819.createBuffer();
o2819.bindBuffer(o2819.PIXEL_UNPACK_BUFFER,o3250);
o3623=o2819.createTexture();
o2819.bindTexture(o2819.TEXTURE_2D,o3623);
o2819.copyTexImage2D(o2819.TEXTURE_2D,2,o2819.RGBA,1,4,8,7,0);
o935.setAttribute('height','9');
o2819.drawElements(o2819.LINE_STRIP,0,o2819.UNSIGNED_BYTE,10);
</script>
ASAN output:
=================================================================
==21389==ERROR: AddressSanitizer: heap-use-after-free on address 0x61e0000504a9 at pc 0x7fc1d0dec464 bp 0x7fff6f759b50 sp 0x7fff6f759b48
WRITE of size 1 at 0x61e0000504a9 thread T0 (file:// Content)
#0 0x7fc1d0dec463 in ~TlsScope /builds/worker/workspace/build/src/gfx/gl/GLContext.h:216:35
#1 0x7fc1d0dec463 in mozilla::WebGLContext::DrawElementsInstanced(unsigned int, int, unsigned int, long, int, char const*) /builds/worker/workspace/build/src/dom/canvas/WebGLContextDraw.cpp:721
#2 0x7fc1cfccc036 in DrawElements /builds/worker/workspace/build/src/dom/canvas/WebGLContext.h:1329:9
#3 0x7fc1cfccc036 in mozilla::dom::WebGL2RenderingContextBinding::drawElements(JSContext*, JS::Handle<JSObject*>, mozilla::WebGL2Context*, JSJitMethodCallArgs const&) /builds/worker/workspace/build/src/obj-firefox/dom/bindings/WebGL2RenderingContextBinding.cpp:10939
#4 0x7fc1d0bf92b1 in mozilla::dom::GenericBindingMethod(JSContext*, unsigned int, JS::Value*) /builds/worker/workspace/build/src/dom/bindings/BindingUtils.cpp:3031:13
#5 0x7fc1d76e46c8 in CallJSNative /builds/worker/workspace/build/src/js/src/vm/JSContext-inl.h:290:15
#6 0x7fc1d76e46c8 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:467
#7 0x7fc1d76ca2f9 in CallFromStack /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:522:12
#8 0x7fc1d76ca2f9 in Interpret(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:3085
#9 0x7fc1d76b638a in js::RunScript(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:417:12
#10 0x7fc1d76e76c4 in js::ExecuteKernel(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value const&, js::AbstractFramePtr, JS::Value*) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:700:15
#11 0x7fc1d76e7e4f in js::Execute(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value*) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:732:12
#12 0x7fc1d81d7129 in ExecuteScript(JSContext*, JS::AutoVector<JSObject*>&, JS::Handle<JSScript*>, JS::Value*) /builds/worker/workspace/build/src/js/src/jsapi.cpp:4748:12
#13 0x7fc1ce4b6836 in nsJSUtils::ExecutionContext::CompileAndExec(JS::CompileOptions&, JS::SourceBufferHolder&, JS::MutableHandle<JSScript*>) /builds/worker/workspace/build/src/dom/base/nsJSUtils.cpp:266:8
#14 0x7fc1d2d14a74 in mozilla::dom::ScriptLoader::EvaluateScript(mozilla::dom::ScriptLoadRequest*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:2321:25
#15 0x7fc1d2d0e4b9 in mozilla::dom::ScriptLoader::ProcessRequest(mozilla::dom::ScriptLoadRequest*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1950:10
#16 0x7fc1d2d0b8e7 in mozilla::dom::ScriptLoader::ProcessInlineScript(nsIScriptElement*, mozilla::dom::ScriptKind) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1591:10
#17 0x7fc1d2ceea7e in mozilla::dom::ScriptLoader::ProcessScriptElement(nsIScriptElement*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1310:10
#18 0x7fc1d2cedb99 in mozilla::dom::ScriptElement::MaybeProcessScript() /builds/worker/workspace/build/src/dom/script/ScriptElement.cpp:141:18
#19 0x7fc1cd26a87b in AttemptToExecute /builds/worker/workspace/build/src/obj-firefox/dist/include/nsIScriptElement.h:247:18
#20 0x7fc1cd26a87b in nsHtml5TreeOpExecutor::RunScript(nsIContent*) /builds/worker/workspace/build/src/parser/html/nsHtml5TreeOpExecutor.cpp:736
#21 0x7fc1cd263d74 in nsHtml5TreeOpExecutor::RunFlushLoop() /builds/worker/workspace/build/src/parser/html/nsHtml5TreeOpExecutor.cpp:540:7
#22 0x7fc1cd26fc6b in nsHtml5ExecutorFlusher::Run() /builds/worker/workspace/build/src/parser/html/nsHtml5StreamParser.cpp:131:20
#23 0x7fc1cb2fd320 in mozilla::SchedulerGroup::Runnable::Run() /builds/worker/workspace/build/src/xpcom/threads/SchedulerGroup.cpp:413:25
#24 0x7fc1cb326ae6 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1040:14
#25 0x7fc1cb342080 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:517:10
#26 0x7fc1cc1f552a in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:97:21
#27 0x7fc1cc147389 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:326:10
#28 0x7fc1cc147389 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:319
#29 0x7fc1cc147389 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:299
#30 0x7fc1d2f5811a in nsBaseAppShell::Run() /builds/worker/workspace/build/src/widget/nsBaseAppShell.cpp:157:27
#31 0x7fc1d7415bfb in XRE_RunAppShell() /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:892:22
#32 0x7fc1cc147389 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:326:10
#33 0x7fc1cc147389 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:319
#34 0x7fc1cc147389 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:299
#35 0x7fc1d74155da in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:718:34
#36 0x4f1875 in content_process_main /builds/worker/workspace/build/src/browser/app/../../ipc/contentproc/plugin-container.cpp:50:30
#37 0x4f1875 in main /builds/worker/workspace/build/src/browser/app/nsBrowserApp.cpp:280
#38 0x7fc1ea9c182f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#39 0x420f48 in _start (/fuzzer3/firefox/firefox+0x420f48)
0x61e0000504a9 is located 41 bytes inside of 2744-byte region [0x61e000050480,0x61e000050f38)
freed by thread T0 (file:// Content) here:
#0 0x4c1952 in __interceptor_free /builds/worker/workspace/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:68:3
#1 0x7fc1d0dcf5f9 in ForceLoseContext /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:1883:5
#2 0x7fc1d0dcf5f9 in mozilla::WebGLContext::EnsureDefaultFB(char const*) /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:785
#3 0x7fc1d0daed2e in ValidateAndInitFB /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:1983:10
#4 0x7fc1d0daed2e in mozilla::WebGLContext::BindCurFBForDraw(char const*) /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:2009
#5 0x7fc1d0de939b in mozilla::ScopedDrawHelper::ScopedDrawHelper(mozilla::WebGLContext*, char const*, unsigned int, mozilla::Maybe<unsigned int> const&, unsigned int, bool*) /builds/worker/workspace/build/src/dom/canvas/WebGLContextDraw.cpp:246:22
#6 0x7fc1d0deb960 in mozilla::WebGLContext::DrawElementsInstanced(unsigned int, int, unsigned int, long, int, char const*) /builds/worker/workspace/build/src/dom/canvas/WebGLContextDraw.cpp:683:28
#7 0x7fc1cfccc036 in DrawElements /builds/worker/workspace/build/src/dom/canvas/WebGLContext.h:1329:9
#8 0x7fc1cfccc036 in mozilla::dom::WebGL2RenderingContextBinding::drawElements(JSContext*, JS::Handle<JSObject*>, mozilla::WebGL2Context*, JSJitMethodCallArgs const&) /builds/worker/workspace/build/src/obj-firefox/dom/bindings/WebGL2RenderingContextBinding.cpp:10939
#9 0x7fc1d0bf92b1 in mozilla::dom::GenericBindingMethod(JSContext*, unsigned int, JS::Value*) /builds/worker/workspace/build/src/dom/bindings/BindingUtils.cpp:3031:13
#10 0x7fc1d76e46c8 in CallJSNative /builds/worker/workspace/build/src/js/src/vm/JSContext-inl.h:290:15
#11 0x7fc1d76e46c8 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:467
#12 0x7fc1d76ca2f9 in CallFromStack /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:522:12
#13 0x7fc1d76ca2f9 in Interpret(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:3085
#14 0x7fc1d76b638a in js::RunScript(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:417:12
#15 0x7fc1d76e76c4 in js::ExecuteKernel(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value const&, js::AbstractFramePtr, JS::Value*) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:700:15
#16 0x7fc1d76e7e4f in js::Execute(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value*) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:732:12
#17 0x7fc1d81d7129 in ExecuteScript(JSContext*, JS::AutoVector<JSObject*>&, JS::Handle<JSScript*>, JS::Value*) /builds/worker/workspace/build/src/js/src/jsapi.cpp:4748:12
#18 0x7fc1ce4b6836 in nsJSUtils::ExecutionContext::CompileAndExec(JS::CompileOptions&, JS::SourceBufferHolder&, JS::MutableHandle<JSScript*>) /builds/worker/workspace/build/src/dom/base/nsJSUtils.cpp:266:8
#19 0x7fc1d2d14a74 in mozilla::dom::ScriptLoader::EvaluateScript(mozilla::dom::ScriptLoadRequest*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:2321:25
#20 0x7fc1d2d0e4b9 in mozilla::dom::ScriptLoader::ProcessRequest(mozilla::dom::ScriptLoadRequest*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1950:10
#21 0x7fc1d2d0b8e7 in mozilla::dom::ScriptLoader::ProcessInlineScript(nsIScriptElement*, mozilla::dom::ScriptKind) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1591:10
#22 0x7fc1d2ceea7e in mozilla::dom::ScriptLoader::ProcessScriptElement(nsIScriptElement*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1310:10
#23 0x7fc1d2cedb99 in mozilla::dom::ScriptElement::MaybeProcessScript() /builds/worker/workspace/build/src/dom/script/ScriptElement.cpp:141:18
#24 0x7fc1cd26a87b in AttemptToExecute /builds/worker/workspace/build/src/obj-firefox/dist/include/nsIScriptElement.h:247:18
#25 0x7fc1cd26a87b in nsHtml5TreeOpExecutor::RunScript(nsIContent*) /builds/worker/workspace/build/src/parser/html/nsHtml5TreeOpExecutor.cpp:736
#26 0x7fc1cd263d74 in nsHtml5TreeOpExecutor::RunFlushLoop() /builds/worker/workspace/build/src/parser/html/nsHtml5TreeOpExecutor.cpp:540:7
#27 0x7fc1cd26fc6b in nsHtml5ExecutorFlusher::Run() /builds/worker/workspace/build/src/parser/html/nsHtml5StreamParser.cpp:131:20
#28 0x7fc1cb2fd320 in mozilla::SchedulerGroup::Runnable::Run() /builds/worker/workspace/build/src/xpcom/threads/SchedulerGroup.cpp:413:25
#29 0x7fc1cb326ae6 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1040:14
#30 0x7fc1cb342080 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:517:10
#31 0x7fc1cc1f552a in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:97:21
#32 0x7fc1cc147389 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:326:10
#33 0x7fc1cc147389 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:319
#34 0x7fc1cc147389 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:299
#35 0x7fc1d2f5811a in nsBaseAppShell::Run() /builds/worker/workspace/build/src/widget/nsBaseAppShell.cpp:157:27
#36 0x7fc1d7415bfb in XRE_RunAppShell() /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:892:22
#37 0x7fc1cc147389 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:326:10
#38 0x7fc1cc147389 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:319
#39 0x7fc1cc147389 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:299
previously allocated by thread T0 (file:// Content) here:
#0 0x4c1c93 in malloc /builds/worker/workspace/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88:3
#1 0x4f26fd in moz_xmalloc /builds/worker/workspace/build/src/memory/mozalloc/mozalloc.cpp:70:17
#2 0x7fc1cd4e0ca0 in operator new /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/mozalloc.h:156:12
#3 0x7fc1cd4e0ca0 in mozilla::gl::GLContextGLX::CreateGLContext(mozilla::gl::CreateContextFlags, mozilla::gl::SurfaceCaps const&, bool, _XDisplay*, unsigned long, __GLXFBConfigRec*, bool, gfxXlibSurface*) /builds/worker/workspace/build/src/gfx/gl/GLContextProviderGLX.cpp:546
#4 0x7fc1cd4e3732 in mozilla::gl::CreateOffscreenPixmapContext(mozilla::gl::CreateContextFlags, mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gl::SurfaceCaps const&, nsTSubstring<char>*) /builds/worker/workspace/build/src/gfx/gl/GLContextProviderGLX.cpp:1007:12
#5 0x7fc1cd4e3abd in mozilla::gl::GLContextProviderGLX::CreateOffscreen(mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gl::SurfaceCaps const&, mozilla::gl::CreateContextFlags, nsTSubstring<char>*) /builds/worker/workspace/build/src/gfx/gl/GLContextProviderGLX.cpp:1034:10
#6 0x7fc1d0dce6d5 in mozilla::CreateGLWithDefault(mozilla::gl::SurfaceCaps const&, mozilla::gl::CreateContextFlags, mozilla::WebGLContext*, std::vector<mozilla::WebGLContext::FailureReason, std::allocator<mozilla::WebGLContext::FailureReason> >*) /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:565:28
#7 0x7fc1d0dcac7f in mozilla::WebGLContext::CreateAndInitGLWith(already_AddRefed<mozilla::gl::GLContext> (*)(mozilla::gl::SurfaceCaps const&, mozilla::gl::CreateContextFlags, mozilla::WebGLContext*, std::vector<mozilla::WebGLContext::FailureReason, std::allocator<mozilla::WebGLContext::FailureReason> >*), mozilla::gl::SurfaceCaps const&, mozilla::gl::CreateContextFlags, std::vector<mozilla::WebGLContext::FailureReason, std::allocator<mozilla::WebGLContext::FailureReason> >*) /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:597:23
#8 0x7fc1d0dcced4 in mozilla::WebGLContext::CreateAndInitGL(bool, std::vector<mozilla::WebGLContext::FailureReason, std::allocator<mozilla::WebGLContext::FailureReason> >*) /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:724:13
#9 0x7fc1d0dd0d32 in mozilla::WebGLContext::SetDimensions(int, int) /builds/worker/workspace/build/src/dom/canvas/WebGLContext.cpp:961:10
#10 0x7fc1d0d1aa0e in mozilla::dom::CanvasRenderingContextHelper::UpdateContext(JSContext*, JS::Handle<JS::Value>, mozilla::ErrorResult&) /builds/worker/workspace/build/src/dom/canvas/CanvasRenderingContextHelper.cpp:243:24
#11 0x7fc1d0d1a4ba in mozilla::dom::CanvasRenderingContextHelper::GetContext(JSContext*, nsTSubstring<char16_t> const&, JS::Handle<JS::Value>, mozilla::ErrorResult&) /builds/worker/workspace/build/src/dom/canvas/CanvasRenderingContextHelper.cpp:197:19
#12 0x7fc1d15241d0 in mozilla::dom::HTMLCanvasElement::GetContext(JSContext*, nsTSubstring<char16_t> const&, JS::Handle<JS::Value>, mozilla::ErrorResult&) /builds/worker/workspace/build/src/dom/html/HTMLCanvasElement.cpp:1016:40
#13 0x7fc1d0646a50 in mozilla::dom::HTMLCanvasElementBinding::getContext(JSContext*, JS::Handle<JSObject*>, mozilla::dom::HTMLCanvasElement*, JSJitMethodCallArgs const&) /builds/worker/workspace/build/src/obj-firefox/dom/bindings/HTMLCanvasElementBinding.cpp:275:49
#14 0x7fc1d0bf92b1 in mozilla::dom::GenericBindingMethod(JSContext*, unsigned int, JS::Value*) /builds/worker/workspace/build/src/dom/bindings/BindingUtils.cpp:3031:13
#15 0x7fc1d76e46c8 in CallJSNative /builds/worker/workspace/build/src/js/src/vm/JSContext-inl.h:290:15
#16 0x7fc1d76e46c8 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:467
#17 0x7fc1d76ca2f9 in CallFromStack /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:522:12
#18 0x7fc1d76ca2f9 in Interpret(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:3085
#19 0x7fc1d76b638a in js::RunScript(JSContext*, js::RunState&) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:417:12
#20 0x7fc1d76e76c4 in js::ExecuteKernel(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value const&, js::AbstractFramePtr, JS::Value*) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:700:15
#21 0x7fc1d76e7e4f in js::Execute(JSContext*, JS::Handle<JSScript*>, JSObject&, JS::Value*) /builds/worker/workspace/build/src/js/src/vm/Interpreter.cpp:732:12
#22 0x7fc1d81d7129 in ExecuteScript(JSContext*, JS::AutoVector<JSObject*>&, JS::Handle<JSScript*>, JS::Value*) /builds/worker/workspace/build/src/js/src/jsapi.cpp:4748:12
#23 0x7fc1ce4b6836 in nsJSUtils::ExecutionContext::CompileAndExec(JS::CompileOptions&, JS::SourceBufferHolder&, JS::MutableHandle<JSScript*>) /builds/worker/workspace/build/src/dom/base/nsJSUtils.cpp:266:8
#24 0x7fc1d2d14a74 in mozilla::dom::ScriptLoader::EvaluateScript(mozilla::dom::ScriptLoadRequest*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:2321:25
#25 0x7fc1d2d0e4b9 in mozilla::dom::ScriptLoader::ProcessRequest(mozilla::dom::ScriptLoadRequest*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1950:10
#26 0x7fc1d2d0b8e7 in mozilla::dom::ScriptLoader::ProcessInlineScript(nsIScriptElement*, mozilla::dom::ScriptKind) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1591:10
#27 0x7fc1d2ceea7e in mozilla::dom::ScriptLoader::ProcessScriptElement(nsIScriptElement*) /builds/worker/workspace/build/src/dom/script/ScriptLoader.cpp:1310:10
#28 0x7fc1d2cedb99 in mozilla::dom::ScriptElement::MaybeProcessScript() /builds/worker/workspace/build/src/dom/script/ScriptElement.cpp:141:18
#29 0x7fc1cd26a87b in AttemptToExecute /builds/worker/workspace/build/src/obj-firefox/dist/include/nsIScriptElement.h:247:18
#30 0x7fc1cd26a87b in nsHtml5TreeOpExecutor::RunScript(nsIContent*) /builds/worker/workspace/build/src/parser/html/nsHtml5TreeOpExecutor.cpp:736
#31 0x7fc1cd263d74 in nsHtml5TreeOpExecutor::RunFlushLoop() /builds/worker/workspace/build/src/parser/html/nsHtml5TreeOpExecutor.cpp:540:7
#32 0x7fc1cd26fc6b in nsHtml5ExecutorFlusher::Run() /builds/worker/workspace/build/src/parser/html/nsHtml5StreamParser.cpp:131:20
#33 0x7fc1cb2fd320 in mozilla::SchedulerGroup::Runnable::Run() /builds/worker/workspace/build/src/xpcom/threads/SchedulerGroup.cpp:413:25
SUMMARY: AddressSanitizer: heap-use-after-free /builds/worker/workspace/build/src/gfx/gl/GLContext.h:216:35 in ~TlsScope
Shadow bytes around the buggy address:
0x0c3c80002040: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3c80002050: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3c80002060: fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa fa
0x0c3c80002070: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c3c80002080: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c3c80002090: fd fd fd fd fd[fd]fd fd fd fd fd fd fd fd fd fd
0x0c3c800020a0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3c800020b0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3c800020c0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3c800020d0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c3c800020e0: fd fd fd fd fd fd fd fd fd fd 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
==21389==ABORTING
|
|
1,444,185 | 13,115,076 |
Created attachment 8957289
prompt.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20180308100121
Steps to reproduce:
Enable WebRender by flipping `gfx.webrender.all` to true in about:config.
Actual results:
Text input field in master password prompt was cut off.
Expected results:
Master password field should look similar to how it looks like without WebRender enabled --> not be cut off.
|
|
1,444,288 | 13,116,003 |
Created attachment 8957429
Screen Shot 2018-03-08 at 11.53.06 PM.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180307211018
Steps to reproduce:
Open a new tab
Actual results:
The Firefox logo appears from the x...
Expected results:
It seems odd that the Firefox logo appears from the X. It looks like a flaw. Image attached.
Sorry, OCD.
|
|
1,444,384 | 13,116,739 |
Created attachment 8957538
Screen Shot 2018-03-09 at 16.08.04.png
Build: 11.0 (9520)
Device: iPhone 8
iOS: 11.0
Pre-requisites:
- Bookmark "youtube.com"
- Play a video on youtube (to appear in search results)
Steps to reproduce:
1. Tap on the URL bar
2. Type "y"
Actual results:
- Bookmarked and history search results are not aligned.
Note:
- Possible regression from Bug 1442838
|
|
1,444,440 | 13,117,226 |
Bug 1441223 added MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED to be emitted when we hit certificates affected by the Symantec distrust.
Some sites are still emitting SEC_ERROR_UNKNOWN_ISSUER if they have multiple certificate trust paths possible, but one is unknown. This error really should be fatal -- perhaps like Bug 1437214.
This affects 60, and is confusing for writing documentation (Bug 1444427). If it's a reasonable patch, we might want to uplift this into 60.
[1] https://tlscanary.mozilla.org/runs/2018-03-08-10-41-46/index.htm
|
|
1,444,473 | 13,117,488 |
This is a follow-up from Bug 1438886, to support ICs calls too, by adding fences after returning from the call with a potentially speculated value.
(see Bug 1438886 comment 13)
|
|
1,444,487 | 13,117,576 |
For now this preference can be manually toggled and will default to false. After other dependencies of the parent bug are addressed and QA has had a chance to test, we can lock this down further.
|
|
1,444,579 | 13,118,580 |
Bug 1433133 removed the `NewTabUtils.placesProvider` reference to the provider, now `browser.topSites.get({providers: ['places']})` returns nothing.
|
|
1,444,599 | 13,118,793 |
we have received a report about this regression in the sumo forum at https://support.mozilla.org/questions/1208595
this behaviour is reproducible and was introduced by bug 517719.
|
|
1,444,668 | 13,119,200 |
The WASM assembler can generate an out-of-range value for |ModuleGenerator::callFarJumps_.jump.offset_|. If it does, it causes SetInt32() (Patching-x86-shared.h) to attempt to write beyond bounds. When this occurs, SetInt32() is called via the following chain:
SetInt32()
^--- SetRel32() (Patching-x86-shared.h)
^--- patchFarJump() (Assembler-x86-shared.h)
^--- ModuleGenerator::finishCode() (WasmGenerator.cpp)
Attached is a POC that causes this write.
The out-of-range value for |offset_| (0xffffffff820206cb in the attached POC) appears to occur because the POC's WASM program is large enough to caused js::jit::X86Encoding::BaseAssembler::m_formatter.m_buffer to contain more than 0x7fffffff bytes.
When ModuleGenerator::finishCode() attempts to link the code, it eventually calls X86Encoding::BaseAssembler::X86InstructionFormatter::immediateRel32(), which contains this code:
5093: m_buffer.putIntUnchecked(0);
5094: return JmpSrc(m_buffer.size());
However, m_buffer.size() returns a |size_t| (64 bits on 64 bit builds) while JmpSrc() takes an |int32_t|. The code here should (but does not) catch this out-of-range value. (Probably some other code should catch it earlier, but I don't understand the assembler well enough to identify that code).
In any case, the bad value propagates back to the caller farJumpWithPatch() (Assembler_x86_shared.h), which calls CodeOffset() (Assembler_shared.h), which puts it, along with the relevant function index, into |callFarJumps_.jump.offset_| (seer ModuleGenerator::linkCallSites()).
Later, when ModuleGenerator::finishCode() calls masm_.patchFarJump(), pathFarJump() computes
code + farJump.offset()
which points well before the start of |code| because offset() is negative.
The result is an attempt to write beyond bounds. This crashes FF 58.0.1 and 58.0.2 x64 release. On at least the debug version of 58.0.2, however, it successfully overwrites something else on the heap.
I found this bug while attempting to force an overflow elsewhere in the WASM assembler. I will report that bug separately.
Use the PoC by starting FF 58.0.1/.2 x64, attaching a debugger to it, and setting a BP in ModuleGenerator::finishCode() where it processes |callFarJumps_|. Put the POC files on a webserver. Load test40.html in FF (you might need to attach the debugger again if a new content process appears), and wait for the BP to fire. When it does, examine |callFarJumps_| and notice that at least one entry contains a negative offset. Trace the code until you hit the
mov dword ptr [r10-4], edx
and watch it either write far beyond bounds or crash with an access violation.
|
|
1,445,028 | 13,123,198 |
From bug 1444564 comment 0,
> 'Firefox Developer Edition Updates' section doesn't work. 'Check for updates'
> button causes error
> > TypeError: gAppUpdater is undefined preferences:1:1
> It is because of bug 1434706.
> https://hg.mozilla.org/mozilla-central/diff/109cd0a34ffe/browser/components/preferences/in-content/main.js#l1.14
|
|
1,445,131 | 13,124,177 |
Double-clicking in the top 10-20 pixels of content area minimizes the whole window on macOS in a new profile. I encountered this while double-clicking in a text field to select all text near the top of a page. I'm not sure what the exact conditions to reproduce are… it seems like some areas don't exhibit the problem e.g. in the BMO search box.
STR:
1) Load any page (AFAICT)
2) Double-click near the top 10-20 pixels in a blank area.
Last good revision: 93b6538bc167b53884d1a8590f0e2f67f124c358
First bad revision: 5e9db9c66ccdbe20d8ebb8c498a4385c4dc54ea0
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=93b6538bc167b53884d1a8590f0e2f67f124c358&tochange=5e9db9c66ccdbe20d8ebb8c498a4385c4dc54ea0
which only contains bug 1401195 which is definitely relevant.
[Tracking Requested - why for this release]: New regression
|
|
1,445,167 | 13,124,423 |
This is blocked by the change to make USER_NON_ADMIN a blacklist in bug 1321724.
USER_NON_ADMIN is only now used by default for the file content process and in bug 1344453 we added a rule to allow read access to all files, so the change to USER_NON_ADMIN should no longer be required.
Try push with everything passing on Linux and some Windows failures due to the USER_NON_ADMIN change:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=0dd5ad56e120d8417cec7883c2d237ace5138e0d
Try push with the USER_NON_ADMIN change backed out:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=bea3a99bb6d43eabb6dafa576ade44dda6abcff1
|
|
1,445,308 | 13,125,442 |
Clear Private Data Crashes the application. Report via email.
|
|
1,445,519 | 13,126,917 |
Created attachment 8958666
testcase
This only seems to happen on macOS with bug 1439875 applied.
Steps to reproduce:
1. open the testcase
2. click the button to open the new window
3. click the button in the new window to open another new window
repeat 3.
Expected result:
All windows should have the same size.
Actual result:
New windows keep shrinking by a titlebar height.
This may be the same issue as bug 1444045, and it doesn't seem to be fixed by current patches in bug 1444525 so it's probably worth separate investigating.
And this is the reason of wpt failure when landing bug 1439875.
|
|
1,445,614 | 13,127,665 |
Currently failure to create an alternate desktop will crash the browser.
It looks like there are cases where this can legitimately fail and certainly chrome only warns.
|
|
1,445,645 | 13,127,906 |
Build: 11.0 (9593)
Device: iPad Air 2
iOS: 11.2.5
Pre-requisits:
- open 3 tabs in this order:
1. google.com
2. mozilla.org
3. bbc.com
- make sure the 1st tab(google.com) is selected
Steps to reproduce:
1. Open Tabs Tray
2. Long tab on the 1st tab(google.com) and move it in the 2nd position
3. Tap on the 3rd tab(bbc.com)
Actual results:
- The tabs will be incorrectly displayed in Top Tabs.
See video here:
- https://www.youtube.com/watch?v=P8gXoSgUmEU
|
|
1,445,943 | 13,130,690 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36
Steps to reproduce:
Currently the only way to manage policies in the Firefox engine on macOS is to utilize CCK2. Since there was a recent implementation for GPO support on the Policy Engine in Firefox (Bug #1433136), I would like to request similar support for macOS which utilizes Configuration Profiles to manage application preferences. The way to do this is to add support for Firefox to make use of Core Foundation so that when a configuration profile is installed, the application can read the preference values that should be getting enforced. More on Core Foundation here: https://developer.apple.com/documentation/corefoundation/preferences_utilities
Commonly, preferences are written to a plist in macOS which contain the preference values that Core Foundation will read from and then set. This is not required but is the common way in which applications tend to write preferences out which could then be managed by a configuration profile.
Ideally, all the current settings that are manageable with CCK2 would be manageable with a Configuration Profile. However, even just having feature parity with GPO support on Firefox on Windows would be great.
Actual results:
Firefox currently does not store preferences in a plist and does not support Configuration Profiles to enforce preferences.
Expected results:
Firefox currently does not store preferences in a plist and does not support Configuration Profiles to enforce preferences.
|
|
1,445,991 | 13,130,985 |
User Agent: Mozilla/5.0 (iPad; CPU OS 11_2_6 like Mac OS X) AppleWebKit/604.5.6 (KHTML, like Gecko) Version/11.0 Mobile/15D100 Safari/604.1
Steps to reproduce:
Upgrade to version 59.0
Navigate to Options:Network Proxy Connection Settings
Reload button next to Auotomatic proxy configuration URL is grayed out even though it’s radio button is selected and the field contains an address
Actual results:
Button is grayed out
Expected results:
Button should be selectable to reload the proxy settings from the URL specfied
|
|
1,446,276 | 13,132,862 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180313132747
Steps to reproduce:
Allowed distro (Xubuntu 16.04 LTS) package manager to upgrade Firefox to 59.0. Restarted Firefox, opened new tab. This has happened on previous upgrades as well, though I don't have the version numbers.
about:config settings previously modified to try to fix this:
- extensions.pocket.api;localhost
- extensions.pocket.enabled;false
- extensions.pocket.site;localhost
Actual results:
"Recommended by Pocket" items present, and clicking gear icon shows "Recommended by Pocket" checkbox is checked. Before upgrade, checkbox was clear and new tabs were empty.
Expected results:
New tab settings from previous version should be maintained. "Recommended by Pocket" should have remained disabled, and checkbox should not have set itself.
|
|
1,446,551 | 13,135,034 |
Sometimes I click the location bar and press enter, but the page does not reload.
Sorry I don't have more precise steps to reproduce.
When it happens, in the browser console I get this stack trace each time I press enter.
too much recursion
next self-hosted:562:9
from self-hosted:597:9
get_children chrome://global/content/bindings/richlistbox.xml:325:28
getIndexOfItem chrome://global/content/bindings/richlistbox.xml:181:13
get_selectedIndex chrome://global/content/bindings/listbox.xml:100:20
get_selectedIndex chrome://global/content/bindings/autocomplete.xml:747:1
handleEnter chrome://browser/content/urlbarBindings.xml:1505:1
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
replayAllDeferredKeyEvents chrome://browser/content/urlbarBindings.xml:474:11
_deferKeyEvent chrome://browser/content/urlbarBindings.xml:424:15
handleEnter chrome://browser/content/urlbarBindings.xml:1526:11
_replayKeyEventInstance chrome://browser/content/urlbarBindings.xml:486:13
|
|
1,446,626 | 13,135,633 |
Created attachment 8959789
background_repaint.zip
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180316220124
Steps to reproduce:
opened the page contained in the archive with Webrender active.
System: AMD Kaveri 7650k, Linux 4.15.9, Mesa-17.3.6, radeonsi, amdgpu
Actual results:
only when scrolling with the mouse, drawing the page in question sometimes takes a long time. however as soon as I click at a not-yet-painted area it is drawn immediatly: https://youtu.be/re5Rkk0LOoY
Looks like some flush operation is missing somewhere.
When scrolled with the keyboard, it works as expected.
Expected results:
WebRender should behave like the OpenGL compositor, and simply redraw previously obscured areas when scrolling.
|
|
1,454,914 | 13,215,121 |
Created attachment 8968859
Screenshots - Edit button.gif
[Affected versions]:
- Nightly 61.0a1, Build ID: 20180417225505
[Affected Platforms]:
- All Windows
- All Mac
- All Linux
[Steps to reproduce]:
1. Open the Firefox browser and navigate to any website.
2. Click the "Page actions" menu and select "Take a Screenshot" option.
3. Skip the onboarding tour.
4. Click the "Save visible" button and select the "Save" button.
5. Observe the "Edit" (Pencil) button.
[Expected result]:
- The button has a blue circle that has a star in it.
[Actual result]:
- The button has no badge.
[Regression]:
- It seems that this is a Nightly regression. Using mozregression tools I have found a regression window. Here are the results:
Last good revision: ae45e56c3c71ae23084e9ef549c3d58880add8a1
First bad revision: 87b552f9c09b68a255eeb84c5c554384b0c1231a
Pushlog: https://goo.gl/pYTBYX
From the pushlog it seems that bug 1452496 has caused this issue.
[Notes]:
- This issue is also reproducible on an older Nightly 61.0a1 build ID 20180108220132 with latest Firefox Screenshots v32.0.0dev installed from here( https://screenshots.dev.mozaws.net/homepage/install-test-local.html ) and on the latest Beta 60.0b13 with latest Firefox Screenshots v30.1.0.
- This issue is not reproducible on the latest Firefox Beta 60.0b12 with Firefox Screenshots v30.1.0.
- This issue is not reproducible on the latest Firefox Release 59.0.2 with Firefox Screenshots v25.0.0.
- Attached is a screen recording with this issue.
|
|
1,455,013 | 13,215,862 |
For more information, see this issue with readability.js:
https://github.com/mozilla/readability/issues/436
|
|
1,455,645 | 13,221,628 |
Created attachment 8969680
console-weird-wrapping.png
**Steps to reproduce**
1. Open the console
2. Evaluate `console.error("fuuu".repeat(100))`
**Actual results**
An horizontal scrollbar is shown on the console, and the arrow icon is shrunk (see attachment)
|
|
1,455,681 | 13,221,961 |
[Affected versions]:
Nightly 60.0a1
[Affected platforms]:
Platforms: Windows 10 x 64, Mac OS X 10.12 and Ubuntu 16.04 x64.
[Steps to reproduce]:
1. Go to "about:preferences" and click on the "Search" field.
2. Start typing to search for something that doesn't have search results in preferences (e.g "SoftVision").
3. Click on "Nightly Support" link.
[Expected result]:
"https://support.mozilla.org/en-US/kb/firefox-options-preferences-and-settings?as=u&utm_source=inproduct"
[Actual result]:
"Nightly Support" link on "Search Results" page isn't working
|
|
1,455,686 | 13,221,977 |
[Affected versions]:
Nightly 61.0a1
[Affected platforms]:
Platforms: Windows 10 x 64, Mac OS X 10.13 and Ubuntu 16.04 x64.
[Steps to reproduce]:
1. Go to "about:preferences#privacy"
2. Under Tracking Protection section, click on "Learn more about Tracking Protection and your privacy" link
3. Observe
[Expected result]:
"https://support.mozilla.org/en-US/kb/tracking-protection?as=u&utm_source=inproduct"
[Actual result]:
"Learn more about Tracking Protection and your privacy" link is not working
|
|
1,455,705 | 13,222,109 |
We passed urls into prefs where hostnames are required. non-socks settings fail due to this.
|
|
1,455,796 | 13,223,044 |
Filed by: dluca [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=174858803&repo=autoland
https://queue.taskcluster.net/v1/task/T4ZjhAO-RUGZoaqtEPe-9A/runs/0/artifacts/public/logs/live_backing.log
|
|
1,455,839 | 13,223,371 |
Created attachment 8969886
Screenshot
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180420220029
Steps to reproduce:
-Opened http://www.faz.net/aktuell/wissen/erde-klima/der-planet-steht-das-system-wankt-der-klimawandel-zeigt-sich-radikaler-denn-je-15545724.html
-Scrolled down
Actual results:
The picture on the top of the article gets sometimes painted on the Chrome.
|
|
1,455,842 | 13,223,399 |
Created attachment 8969891
Recording FPS drops.mp4
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180421100143
Steps to reproduce:
Unfortunately this can only be reproduced while being logged in.
Viewed a topic on https://www.ip-phone-forum.de/forums/
Scrolled down to the bottom of the page.
Actual results:
When you scroll over the quick answer box FPS drop heavily. If you scroll very fast, you can produce single digit FPS . There's just one "scroll step" when using mouse wheel scroll where this happens, both when scrolling up and down. All other steps are fine.
I can only reproduce this on a Radeon R9 390, not on an Intel HD Graphics on Windows 10.
Expected results:
FPS stay at 60 like on the rest of the page while scrolling.
|
|
1,455,898 | 13,223,667 |
Created attachment 8969935
attack.html - example exploit
VULNERABILITY DETAILS
An attacker can combine complicated CSS effects and the :visited selector to
reliably determine the visited status of arbitrary URLs, by forcing the browser
to complete expensive repaint operations if a test URL is visited, and comparing
performance measurements with those taken for a known-unvisited "control" URL.
(1) The attacker constructs an element that is complicated to render using CSS
effects.
In the attached exploit, we use the following inline style (crafted through
manual trial and error) to produce a link element that is costly to paint:
display: inline-block;
width: 5px; font-size: 2px; text-align: center;
outline-width: 24px; text-shadow: 16px 16px 10px #fefffe;
filter: contrast(200%) drop-shadow(16px 16px 10px #fefefe) saturate(200%);
transform: perspective(100px) rotateY(37deg);
To further increase the burden placed on the browser's rendering engine, the
element is filled with a long string of Chinese characters. The exact
configuration is less important than the overall idea that the element is made
costly to draw by stacking on these challenges.
(2) The attacker forces the browser to repeatedly repaint the element if the
test URL is visited.
We use the CSS :visited selector to apply different color styles to the link
element if it points to a visited URL. For example:
a { color: white; background-color: white; outline-color: white; }
a:visited { color: #feffff; background-color: #fffeff;
outline-color: #fffffe; }
In the attached attack, we use the DOM to oscillate the link element's href
attribute between the test URL and a randomly-generated known-unvisited URL,
forcing a repaint with each oscillation if the test URL is visited.
An attacker could alternatively point the link to the test URL, then rotate the
colors of the CSS rules under :visited through a set of different values. This
similarly forces the browser to repeatedly repaint the element if the test uRL
is visited.
(3) The attacker measures paint performance during the process in step (2) and
compares it with measurements taken for a known-unvisited control URL.
We measure the frequency of `requestAnimationFrame` callback executions over
time. The forced repaints cause a drop in this measurement if the test URL is
visited, relative to one collected for the control URL; thus we can make
a visited vs unvisited determination.
Experimentally, 70-80% fewer `requestAnimationFrame` callbacks fire in the case
of a visited test URL vs the control URL, with the effect observable down to
100ms measurement periods (producing measurements on the order of 4 vs 15). An
attacker using an intelligent search strategy could rapidly extract
visited/unvisited status for each of a set of test URLs.
VERSION (tested on 2 systems)
Firefox Version: 59.0.2 (64-bit) stable
Operating System: Windows 10 Pro Version 1709 (OS Build 16299.371)
Firefox Version: 59.0.2 (64-bit) stable
Operating System: macOS 10.10.5
REPRODUCTION CASE
`attack.html` demonstrates inferring visited status of arbitrary URLs through
the technique described above. If it does not seem to work, ensure that your
Firefox installation can properly display Chinese characters.
|
|
1,455,908 | 13,223,712 |
Created attachment 8969943
screenshot
Reproducible: not always
Steps To reproduce:
1. Open Youtube video
2. Move the seek bar to the uncached part
Actual Results:
Sometimes, Graphical glitch on loading spinner.
See attached screenshot.
|
|
1,456,082 | 13,226,229 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180419200216
Steps to reproduce:
Open a new tab. (not the one that appears at the start.)
Actual results:
It shows a completely white screen with the title : New Tab
See this : https://i.imgur.com/J4bTUYL.png
Expected results:
It should have showed the normal new tab, which it shows when Firefox starts for the first time. (or while opening a new tab)
Like this : https://i.imgur.com/0kj1utf.png
|
|
1,456,445 | 13,229,259 |
Created attachment 8970508
go to download page doesnt work.gif
[Affected versions]:
- Nightly 61.0a1, Build ID 20180422223305
[Affected Platforms]:
- All Windows
- All Linux
[Prerequisites]:
- Have a clean new Firefox profile.
- Have a download card in the Highlights section.
[Steps to reproduce]:
1. Start the browser with the profile from prerequisites.
2. Open a new tab and click the "..." button for the Download card.
3. Click the "Go to download page" option and observe the behavior.
[Expected result]:
- A new tab is opened with the site the donwload was made.
[Actual results]:
- Nothing happens.
[Notes]:
- The issue is not reproducible on Mac OS.
- Attached a screen recording of the issue.
|
|
1,456,485 | 13,229,572 |
Created attachment 8970546
pdf pages.gif
[Affected versions]:
- Nightly 61.0a1 (Build ID: 20180424013604)
- Beta 60.0b14 (Build ID: 20180419200216)
[Affected Platforms]:
- All Windows
- All Mac
- All Linux
[Prerequisites]:
- Have a clean Firefox profile.
- Screenshots onboarding tour was already visited.
[Steps to reproduce]:
1. Open the latest Nightly build with the profile from prerequisites.
2. Navigate to a PDF page (eg: http://www.pdf995.com/samples/pdf.pdf).
3. Click the "Take a Screenshot" button from "Page Actions" menu.
4. Observe the behavior.
[Expected result]:
- The Screenshots overlay is displayed and you can make a selection.
[Actual results]:
- "We can't screenshot this page" error is displayed.
[Regression]:
- The issue is not reproducible on latest Firefox 59.0.2 release. Considering this I have found the regression window using the mozregression tools. Here are the results:
- Last good revision: c8514e653b71479ba22a307f58f79f563ed80e9d
- First bad revision: 07ab807639ee42a407a9bdb0d374206c0f17678d
- Pushlog: https://goo.gl/aLWFGg
Looks like Bug 1436482 introduced this issue, but I am not sure if this should be fixed on the Screenshots or Nightly side.
[Notes]:
- Attached a screen recording with the issue.
|
|
1,456,522 | 13,229,864 |
I believe bug 1439834 broke this.
|
|
1,456,652 | 13,231,210 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
Steps to reproduce:
1. Go to https://test.shhnjk.com/read_bypass.html
2. Click reader view icon
3. Click on "Click ME" link
4. Exit Reader view in new tab
Actual results:
SameSite cookie not sent.
Expected results:
SameSite cookie is sent when exiting Reader view at the end.
Firefox doesn't fully track "Site for cookie" when exiting Reader view. Using various tricks in Reader view (target blank with # and meta refresh), attacker can start Reader view from attacker site and navigate to victim site without exiting Reader view. Which makes it possible to end in a state where Reader view holds CSRF payload within Reader view, and it is triggered when exiting Reader view.
|
|
1,456,923 | 13,233,121 |
Nightly 61.0a1 (2018-04-25) (64-bit) seems to break switching to dev-tools panels that are loaded temporarily. Mozregression leads me to Bug 1441070 from the following results:
26:07.02 INFO: Last good revision: be5ba8b6dea2d025e0e1f7268336e1d1f0c32399
26:07.02 INFO: First bad revision: 3577a6b9b1a13a0dfd93073f4ef9209c08764eb4
Steps to reproduce:
- Download https://github.com/karolien/media-devtools-panel-react
- Navigate to about:debugging
- Click load temporary add-on, navigate to {location-of-download}/media-devtools-panel-react/extension/ and select any file to load the add-on.
- Open the Developer Tools, and attempt to show the "Media" tab.
Expected results:
- See the media panel
Actual results:
- Does not switch away from current panel
This worked as of 4/24, but stopped working this morning, 4/25.
|
|
1,456,975 | 13,233,545 |
Created attachment 8971011
minimized-from-67447ff63f6161ff7b3a7220157c2bebec80051f
The bug is triggered here https://searchfox.org/mozilla-central/source/image/decoders/icon/nsIconURI.cpp#103 because there exists some path in the IPC that sets mIconSize without validating it.
If you want access to bug 1451859 so you can reproduce, let me know and I can CC you.
osboxes@osboxes:~/mozilla-central$ (cd obj-x86_64-pc-linux-gnu/dist/bin/; MOZ_RUN_GTEST=1 LIBFUZZER=1 FUZZER=ContentParentIPC ./firefox -artifact_prefix=/home/osboxes/content-parent-artifacts/ /home/osboxes/content-parent-artifacts/minimized-from-67447ff63f6161ff7b3a7220157c2bebec80051f -len_control=0 -max_len=384 -rss_limit_mb=0 -close_fd_mask=2)
Running Fuzzer tests...
INFO: Seed: 3613430132
INFO: Loaded 1 modules (1636978 guards): 1636978 [0x7fbca02a7d80, 0x7fbca08e6748),
./firefox: Running 1 inputs 1 time(s) each.
Running: /home/osboxes/content-parent-artifacts/minimized-from-67447ff63f6161ff7b3a7220157c2bebec80051f
=================================================================
==29686==ERROR: AddressSanitizer: SEGV on unknown address 0x7fc039beeec8 (pc 0x7fbc8b0bab23 bp 0x7ffd3e64fed0 sp 0x7ffd3e64fd40 T0)
==29686==The signal is caused by a READ memory access.
#0 0x7fbc8b0bab22 in nsTSubstring<char>::Append(char const*, unsigned int) /home/osboxes/mozilla-central/obj-x86_64-pc-linux-gnu/dist/include/nsTSubstring.h:368:31
#1 0x7fbc8b0bab22 in nsTSubstring<char>::operator+=(char const*) /home/osboxes/mozilla-central/obj-x86_64-pc-linux-gnu/dist/include/nsTSubstring.h:503
#2 0x7fbc8b0bab22 in nsMozIconURI::GetSpec(nsTSubstring<char>&) /home/osboxes/mozilla-central/image/decoders/icon/nsIconURI.cpp:103
#3 0x7fbc95ffa6c0 in nsNavHistory::CanAddURI(nsIURI*, bool*) /home/osboxes/mozilla-central/toolkit/components/places/nsNavHistory.cpp:923:23
#4 0x7fbc95ffefc8 in mozilla::places::History::SetURITitle(nsIURI*, nsTSubstring<char16_t> const&) /home/osboxes/mozilla-central/toolkit/components/places/History.cpp:3017:29
#5 0x7fbc90989f6a in mozilla::dom::ContentParent::RecvSetURITitle(mozilla::ipc::URIParams const&, nsTString<char16_t> const&) /home/osboxes/mozilla-central/dom/ipc/ContentParent.cpp:3625:14
#6 0x7fbc889eb514 in mozilla::dom::PContentParent::OnMessageReceived(IPC::Message const&) /home/osboxes/mozilla-central/obj-x86_64-pc-linux-gnu/ipc/ipdl/PContentParent.cpp:4458:20
#7 0x7fbc9813bc18 in void mozilla::ipc::FuzzProtocol<mozilla::dom::ContentParent>(mozilla::dom::ContentParent*, unsigned char const*, unsigned long, std::unordered_set<unsigned int, std::hash<unsigned int>, std::equal_to<unsigned int>, std::allocator<unsigned int> >&) /home/osboxes/mozilla-central/obj-x86_64-pc-linux-gnu/dist/include/ProtocolFuzzer.h:48:18
#8 0x7fbc9813ae26 in RunContentParentIPCFuzzing(unsigned char const*, unsigned long) /home/osboxes/mozilla-central/dom/ipc/fuzztest/content_parent_ipc_libfuzz.cpp:67:3
#9 0x5ee47d in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) /home/osboxes/mozilla-central/tools/fuzzing/libfuzzer/FuzzerLoop.cpp:517:13
#10 0x5c65ef in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /home/osboxes/mozilla-central/tools/fuzzing/libfuzzer/FuzzerDriver.cpp:280:6
#11 0x5d2a21 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) /home/osboxes/mozilla-central/tools/fuzzing/libfuzzer/FuzzerDriver.cpp:703:9
#12 0x7fbc967101e1 in mozilla::FuzzerRunner::Run(int*, char***) /home/osboxes/mozilla-central/tools/fuzzing/interface/harness/FuzzerRunner.cpp:60:10
#13 0x7fbc96621528 in XREMain::XRE_mainStartup(bool*) /home/osboxes/mozilla-central/toolkit/xre/nsAppRunner.cpp:4021:35
#14 0x7fbc96636196 in XREMain::XRE_main(int, char**, mozilla::BootstrapConfig const&) /home/osboxes/mozilla-central/toolkit/xre/nsAppRunner.cpp:4957:12
#15 0x7fbc96637e6d in XRE_main(int, char**, mozilla::BootstrapConfig const&) /home/osboxes/mozilla-central/toolkit/xre/nsAppRunner.cpp:5064:21
#16 0x51ea9c in do_main(int, char**, char**) /home/osboxes/mozilla-central/browser/app/nsBrowserApp.cpp:231:22
#17 0x51ea9c in main /home/osboxes/mozilla-central/browser/app/nsBrowserApp.cpp:304
#18 0x7fbcad9eb1c0 in __libc_start_main /build/glibc-itYbWN/glibc-2.26/csu/../csu/libc-start.c:308
#19 0x421bc9 in _start (/home/osboxes/mozilla-central/obj-x86_64-pc-linux-gnu/dist/bin/firefox+0x421bc9)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/osboxes/mozilla-central/obj-x86_64-pc-linux-gnu/dist/include/nsTSubstring.h:368:31 in nsTSubstring<char>::Append(char const*, unsigned int)
==29686==ABORTING
MS: 0 ; base unit: 0000000000000000000000000000000000000000
0x28,0x0,0x0,0x0,0xff,0xff,0xff,0x7f,0x97,0x0,0x2d,0x0,0x45,0x6e,0x76,0x50,0x6c,0x69,0x67,0x6e,0x75,0x7b,0x6c,0x75,0x67,0x6e,0x73,0x0,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x1,0x0,0x0,0x0,0x9b,0x9a,0x9a,0xba,0x73,0x0,0x0,0x0,0x0,0x78,0x69,0x74,0x63,0x6f,0x64,0x65,0x65,0x72,0x5f,0x73,0x6d,0x78,0x69,0x74,0x63,0x0,0x0,0x72,0x5f,0x73,0x6d,0x61,
(\x00\x00\x00\xff\xff\xff\x7f\x97\x00-\x00EnvPlignu{lugns\x00\x00\x00\x00\x00\x04\x00\x00\x00\x01\x00\x00\x00\x9b\x9a\x9a\xbas\x00\x00\x00\x00xitcodeer_smxitc\x00\x00r_sma
|
|
1,457,252 | 13,236,374 |
Created attachment 8971353
Applications section sub-dialog does not display buttons properly.JPG
[Affected versions]:
Nightly 60.0a1
[Affected platforms]:
Platforms: Windows 10 x 64, Mac OS X 10.12 and Ubuntu 16.04 x64.
[Steps to reproduce]:
1. Go to "about:preferences" using Italian locale
2. Under "Application" press the irc (action section drop-down) => Always ask => Application Details
3. Observe the dialog
AR: Application details sub-dialog does not display the buttons properly
ER: Application details sub-dialog should be displayed properly
|
|
1,457,284 | 13,236,561 |
Created attachment 8971370
add Skia m66 cherry-picks
[Tracking Requested - why for this release]:
Skia's m66 branch (https://skia.googlesource.com/skia/+/chrome/m66) has included some new cherry-picks to deal with various security bugs, so we should take these before 60 beta hits release.
These are just changes that have already been rolled into their branch since weeks ago, so they should be safe for us to take.
|
|
1,457,499 | 13,238,575 |
Created attachment 8971623
Eastward - Bande-annonce 2018.png
Since a few days when playing some videos I have a green band on top.
For example : https://www.dailymotion.com/video/x6ign45
With 720p quality only gives me gives me *see attachment.
|
|
1,457,927 | 13,243,440 |
Created attachment 8972017
rec of the issue.gif
[Notes]:
- If there are no "Bookmarks" or "Pocket" saves in the "Highlights" area, the most recent download is correctly displayed on the first position.
[Affected versions]:
- Nightly 61.0a1, Build ID 20180430100522
[Affected Platforms]:
- All Windows
- All Mac
- All Linux
[Prerequisites]:
- Have a clean new Firefox profile.
- Have the "Highlights" section populated with "Bookmarks" and "Pocket" cards.
[Steps to reproduce]:
1. Start the browser with the profile from prerequisites.
2. Navigate to any website (eg. https://www.thinkbroadband.com/download) and download any file.
3. Open a new tab and observe the "Highlights" area.
[Expected result]:
- The most recent download is displayed first in the "Highlights" area.
[Actual results]:
- The most recent download is displayed last in the "Highlights" area.
[Additional Notes]:
- The issue is still reproducible after browser restart.
- Attached a screen recording of the issue.
|
|
1,458,048 | 13,244,698 |
sctp_load_addresses_from_init() (netwerk\sctp\src\netinet\sctp_pcb.c) is likely to write beyond bounds if the INIT argument it parses does not include an |SCTP_RANDOM| parameter. The argument comes from a (presumably untrusted) network source.
The bug is in the calculation of |keylen|. Lines 7740-44 calculate |keylen| and allocate |sizeof (sctp_key_t) + keylen| bytes. But if there is no |SCTP_RANDOM| parameter in the INIT, control skips lines 7562-82, and |p_random| is NULL (its initial value, set by line 7120) when control reaches line 7739:
7100: int
7101: sctp_load_addresses_from_init(struct sctp_tcb *stcb, struct mbuf *m,
7102: int offset, int limit,
7103: struct sockaddr *src, struct sockaddr *dst,
7104: struct sockaddr *altsa, uint16_t port)
7105: {
7106: /*
7107: * grub through the INIT pulling addresses and loading them to the
7108: * nets structure in the asoc. The from address in the mbuf should
7109: * also be loaded (if it is not already). This routine can be called
7110: * with either INIT or INIT-ACK's as long as the m points to the IP
7111: * packet and the offset points to the beginning of the parameters.
7112: */
...
7120: struct sctp_auth_random *p_random = NULL;
7121: uint16_t random_len = 0;
...
7131: uint32_t keylen;
7132: int got_random = 0, got_hmacs = 0, got_chklist = 0;
...
7237: /* now we must go through each of the params. */
7238: phdr = sctp_get_next_param(m, offset, ¶m_buf, sizeof(param_buf));
7239: while (phdr) {
7240: ptype = ntohs(phdr->param_type);
7241: plen = ntohs(phdr->param_length);
...
7562: } else if (ptype == SCTP_RANDOM) {
7563: if (plen > sizeof(random_store))
7564: break;
7565: if (got_random) {
7566: /* already processed a RANDOM */
7567: goto next_param;
7568: }
7569: phdr = sctp_get_next_param(m, offset,
7570: (struct sctp_paramhdr *)random_store,
7571: plen);
7572: if (phdr == NULL)
7573: return (-26);
7574: p_random = (struct sctp_auth_random *)phdr;
7575: random_len = plen - sizeof(*p_random);
7576: /* enforce the random length */
7577: if (random_len != SCTP_AUTH_RANDOM_SIZE_REQUIRED) {
7578: SCTPDBG(SCTP_DEBUG_AUTH1, "SCTP: invalid RANDOM len\n");
7579: return (-27);
7580: }
7581: got_random = 1;
7582: } ...
...
7668: next_param:
7669: offset += SCTP_SIZE32(plen);
7670: if (offset >= limit) {
7671: break;
7672: }
7673: phdr = sctp_get_next_param(m, offset, ¶m_buf,
7674: sizeof(param_buf));
7675: }
...
...This, in turn, means that line 7748...
7739: /* concatenate the full random key */
7740: keylen = sizeof(*p_random) + random_len + sizeof(*hmacs) + hmacs_len;
7741: if (chunks != NULL) {
7742: keylen += sizeof(*chunks) + num_chunks;
7743: }
7744: new_key = sctp_alloc_key(keylen);
7745: if (new_key != NULL) {
7746: /* copy in the RANDOM */
7747: if (p_random != NULL) {
...which resets |keylen| to properly index into |new_key->key|, will not be executed...
7748: keylen = sizeof(*p_random) + random_len;
7749: memcpy(new_key->key, p_random, keylen);
7750: }
And that means that lines 7752-61 use the old value of |keylen| for addressing the destinations of the memcpy()s on lines 7753-54 and 7759-60. But this value is actually the length, in bytes, of |new_key->key|, so both memcpy()s will write beyond bounds:
7751: /* append in the AUTH chunks */
7752: if (chunks != NULL) {
7753: memcpy(new_key->key + keylen, chunks,
7754: sizeof(*chunks) + num_chunks);
7755: keylen += sizeof(*chunks) + num_chunks;
7756: }
7757: /* append in the HMACs */
7758: if (hmacs != NULL) {
7759: memcpy(new_key->key + keylen, hmacs,
7760: sizeof(*hmacs) + hmacs_len);
7761: }
7762: } else {
7763: /* failed to get memory for the key */
7764: return (-34);
7765: }
...
7772: return (0);
7773: }
Nothing in the function prevents control from reaching lines 7740 et seq if a |SCTP_RANDOM| parameter is not present.
I'll try to produce a POC.
|
|
1,458,246 | 13,246,165 |
STEPS TO REPRODUCE:
1) Start today's Mac nightly (official nightly, built from rev d2a4720d1c33).
2) Install Gecko profiler addon from https://perf-html.io/
3) Set the profiler to sample every 0.2ms with a 630MB buffer.
4) Start the profiler.
5) Load https://1yzzl25mwj.codesandbox.io/
6) Once the frame counter thing gets to 100/100 and shows per/frame times,
hit Ctrl+Shift+2.
EXPECTED RESULTS: I get a profile of that page.
ACTUAL RESULTS: Page crashes. I do not actually get a profile for the PID the page was loaded in. An example crash is at https://crash-stats.mozilla.com/report/index/0323f22b-1a5f-48cd-b609-9be8b0180501 and as mstange noted on IRC the "MOZ_CRASH(IPC message size is too large)" bit is likely the cause...
|
|
1,458,373 | 13,247,247 |
Created attachment 8972456
Screen Shot 2018-05-01 at 17.33.01.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180427102245
Steps to reproduce:
Visit http://diana-adrianne.com/purecss-francine/ and scroll down until the head intersects the top of the window.
Actual results:
Parts of the hair were rendered as colored rectangles in the URL / tab bar.
Expected results:
The image should be confined to the boundaries of the page.
|
|
1,458,449 | 13,247,768 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180430220108
Steps to reproduce:
Opened ftp://ftp.fu-berlin.de/doc/rfc/authors/rfc7430.xml from Google
Actual results:
I was slapped in the face by a wall of text, no for real:
Firefox blocked the stylesheet (xslt file) from loading.
console log:
"Loading FTP subresource within http(s) page not allowed (Blocked loading of: “ftp://ftp.fu-berlin.de/doc/rfc/authors/rfc2629.xslt”)"
My problem: it's within an ftp page/document and not an http page
Is this a bug or desired?
If it's desired, then the error needs to be adjusted.
Expected results:
I'm not sure if it makes sense, to block stylesheets, if the xml or even html is located on the same ftp server already.
If you don't want this, then you should block html/xml from ftp all together instead of showing the user incomplete documents.
Also: Downloading the xml file (whole website), doesn't download the xslt file, so opening it locally doesn't work without downloading the files one by one (taking a look at the source file to get required URLs)
Which means: you cannot read those documents unless you get a real FTP client or learn xml.
Another bug:
Firefox tries to render the xslt file for some reason, thereby complicating the download, since I have to click "view source" in the context menu first, to be able to save the page.
STRG+S on the open xslt file doesn't select the correct file name and tries to save it as html.
I could open another bug report for this, if you think it's different enough.
|
|
1,458,553 | 13,248,733 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180426170554
Steps to reproduce:
This issue is very similar to bug 1422027
I have a Macbook Pro 11,3 with Intel Iris Pro 5200 and Nvidia GeForce GT 750M and am using the updated Nvidia Web Driver.
With the Nvidia Web Driver installed, navigate to Google Maps.
Actual results:
When I go to Google Maps, the map navigation is very slow and the map is occasionally all black or blinks black especially while trying to zoom in or out. It is unusable.
Expected results:
Google Maps should work normally.
mozregression:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4536fd333b16bfa86eb1fdf94616d2d067bfc41f&tochange=a678eec13c6e6bf1662cc4db5719bbb413c63f65
|
|
1,458,720 | 13,250,776 |
(In reply to :Ehsan Akhgari from bug 1450630 comment #14)
...
> (In reply to David Keeler [:keeler] (use needinfo) from bug 1450630 comment #13)
> > I'm confused - DataStorage was written with the intent that it be safe to
> > access from multiple threads (the documentation even says so at the top of
> > DataStorage.h). From what I can tell from the code, the static
> > DataStorage::Get* meta-APIs that operate on the different types of
> > DataStorage we have are main-thread-only, but are the Get/Set/Remove APIs
> > that operate on actual data restricted as well? If so, we've strayed from
> > the original design requirements (e.g. nsSiteSecurityService is
> > fundamentally broken if we can't access its backing DataStorage off the main
> > thread).
>
> Hmm... I'm not sure what the API requirements here are, I'm basing my
> judgement on what the code is actually doing. All calls to
> RunOnAllContentParents() require to be on the main thread (in general, our
> IPC interfaces are not thread safe so if the caller requires thread safety
> it is its own responsibility to take care of that at layers higher than IPC.)
>
> This code is currently called from Put(), Remove() and Clear() so per above
> I think you're suggesting that this has all been broken since bug 1215723
> (Firefox 45)? If yes, then the right fix isn't to fix the Necko consumers,
> but to rework the fix to bug 1215723 to make it not have a main-thread
> dependency. I think doing so is actually relatively easy, all that should
> be required is to rewrite RunOnAllContentParents() to make it dispatch a
> runnable to the main thread if we aren't there currently, and make sure its
> callers capture their closure with a copy rather than by reference.
|
|
1,458,856 | 13,251,771 |
[Description:]
The following reproduces only on a FF client when using a new non-existent preference added manually from about:config.
[Prerequisites:]
You need access to New Admin interface (https://normandy-admin.stage.mozaws.net/control-new)
1. Set the app.normandy.dev_mode preference to true to run recipes immediately on startup.
2. Set the app.normandy.logging.level preference to 0 to enable more logging.
3. Set 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.
4. Set the preference value for app.normandy.api_url set to https://normandy.stage.mozaws.net/api/v1
[Steps:]
1. Open Firefox client with a new profile.
2. Open about:config in a new tab and right click and add a new preferences: e.g. non_existent_preference, int, with value 10.
3. Open Admin center and create a new rollout type recipe, targeting the step2 preference, changing the value to something else, e.g. 12.
4. Publish step 3 recipe.
5. On the profile from step 1, set prerequisites and restart.
6. Open browser console and check the results.
[Actual Result:]
1525337683826 app.normandy.recipe-runner INFO Executing recipe "pref-r-2" (action=preference-rollout)
[Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getIntPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource://normandy/lib/PrefUtils.jsm :: getPref :: line 34" data: no]
getPref resource://normandy/lib/PrefUtils.jsm:34:16 _run/newRollout.preferences< resource://normandy/actions/PreferenceRolloutAction.jsm:41:24 map self-hosted:292:17 _run resource://normandy/actions/PreferenceRolloutAction.jsm:38:20 InterpretGeneratorResume self-hosted:1264:8
[Expected Result:]
The preference rollout should be executed successfully with no browser console error.
|
|
1,458,906 | 13,252,208 |
Created attachment 8972884
rec of the issue.gif
[Affected versions]:
- Firefox Beta 60.0b16
- Nightly 61.0a1
[Affected Platforms]:
- All Windows
- All Mac
- All Linux
[Prerequisites]:
- Have a clean new Firefox profile.
- Have the set-up for the "Title 1" variant configured (https://goo.gl/cL4Ue3).
[Steps to reproduce]:
1. Start the browser with the profile from prerequisites.
2. Open two new tabs and click the "Customize your New Tab page" button from the top right part of the page.
3. Uncheck the "Sponsored Stories" option.
4. Open a new tab and observe the "Recommended by Pocket" area.
[Expected result]:
- Only the "Pocket" recommendations cards are displayed.
[Actual results]:
- A "Sponsored content" card is also displayed.
[Additional Notes]:
- The issue is reproducible for all the variants except "Control".
- This issue is no longer reproducible for the next new tabs opened.
- Attached a screen recording of the issue.
|
|
1,458,956 | 13,252,665 | null |
|
1,458,997 | 13,252,983 |
Created attachment 8972981
Dark Theme Toolbar Flicker.mov
Nightly 61.0a1 (2018-05-03) (64-Bit)
macOS 10.12.6
STR:
1.) Use the official Dark Theme
2.) Start Nightly
3.) Take a look at the Toolbar, when Nightly starts
Actual: The Toolbar flickers for a short moment.
Expected: No flicker.
This is a regression in latest Nightly.
A screencast is attached.
Thanks,
Mehmet
|
|
1,459,195 | 13,254,592 |
Created attachment 8973201
screenshot
Steps To Reproduce:
1. Open https://cyanharlow.github.io/purecss-francine/
2. Wait for render the page
3. Try scroll down
Actual Results:
See attached screenshot
|
|
1,459,295 | 13,255,490 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180504100129
Steps to reproduce:
1. go to bestbuy.com
2. Login will fail despite verified credentials
Actual results:
Cannot login to the website.
Expected results:
Login should have suceeded as on MS-Edge browser
|
|
1,459,383 | 13,256,243 |
Created attachment 8973400
FireFox_IndexDB_UAF.html
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Steps to reproduce:
run firefox with attached html
Actual results:
https://searchfox.org/mozilla-central/source/dom/indexedDB/KeyPath.cpp#323
nsresult
KeyPath::ExtractKey(JSContext* aCx, const JS::Value& aValue, Key& aKey) const
{
uint32_t len = mStrings.Length();
JS::Rooted<JS::Value> value(aCx);
aKey.Unset();
for (uint32_t i = 0; i < len; ++i) {
nsresult rv = GetJSValFromKeyPathString(aCx, aValue, mStrings[i],
value.address(),
DoNotCreateProperties, nullptr,
nullptr);
if (NS_FAILED(rv)) {
return rv;
}
if (NS_FAILED(aKey.AppendItem(aCx, IsArray() && i == 0, value))) {
NS_ASSERTION(aKey.IsUnset(), "Encoding error should unset");
return NS_ERROR_DOM_INDEXEDDB_DATA_ERR;
}
}
aKey.FinishArray();
return NS_OK;
}
GetJSValFromKeyPathString can execute js callback by setting a getter. In the callback, one can call deleteIndex free the KeyPath now using, which make mStrings invalid.
|
|
1,459,404 | 13,256,428 |
Created attachment 8973441
leakjsonSandbox.zip
When calling browser.storage.sync.get (and set?), then the jsonSandbox (created via [1], [2] and [3]) is leaked when the page is closed:
chrome.storage.sync.get({booleanValue: true}, function(items) {});
If a temporary add-on ID is used (i.e. manifest.json does not have applications.gecko.id), then the content script sandbox is leaked too, but only if a property of the resolved storage object is accessed:
chrome.storage.sync.get({booleanValue: true}, function(items) { void items.booleanValue; });
chrome.storage.sync.get({booleanValue: true}, function(items) {});
// ^ The last does not leak the content script sandbox, the first does.
STR.
1. Put page.html (in leakjsonSandbox.zip) on a server, e.g. at localhost
2. Load the extension (leakjsonSandbox.zip).
3. Open about:memory
4. Open page.html
5. Follow the instructions at page.html (basically create 10 frames, then remove those frames).
In about:memory, the leaked sandboxes can be found by searching for "leaky, moz".
To reproduce the content script sandbox leakage, unzip the extension, edit manifest.json and remove the "applications" section.
Reproduced in Firefox 59.0.2 and Firefox Nightly 20180504220115
[1]: https://searchfox.org/mozilla-central/rev/c0d81882c7941c4ff13a50603e37095cdab0d1ea/toolkit/components/extensions/ExtensionCommon.jsm#259-268
[2]: https://searchfox.org/mozilla-central/rev/53afcfdbabed96883126d0ebbcac499b358e32f2/toolkit/components/extensions/child/ext-storage.js#66-81
[3]: https://searchfox.org/mozilla-central/rev/53afcfdbabed96883126d0ebbcac499b358e32f2/toolkit/components/extensions/child/ext-storage.js#119-121
|
|
1,459,697 | 13,260,284 |
Created attachment 8973771
testcase.html
Found with m-c:
BuildID=20180507140941
SourceStamp=93443d36d4bd53dba004f7b73430879f96daa681
==25250==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00000056d5d8 bp 0x7ffe1fbede30 sp 0x7ffe1fbedcc0 T0)
==25250==The signal is caused by a WRITE memory access.
==25250==Hint: address points to the zero page.
#0 0x56d5d7 in MOZ_CrashPrintf src/mfbt/Assertions.cpp:63:3
#1 0x7f3dbab4cc6b in InvalidArrayIndex_CRASH(unsigned long, unsigned long) src/xpcom/ds/nsTArray.cpp:26:3
#2 0x7f3dc2dc4b6a in ElementAt src/obj-firefox/dist/include/nsTArray.h:1041:7
#3 0x7f3dc2dc4b6a in operator[] src/obj-firefox/dist/include/nsTArray.h:1070
#4 0x7f3dc2dc4b6a in nsFloatManager::EllipseShapeInfo::LineEdge(int, int, bool) const src/layout/generic/nsFloatManager.cpp:1007
#5 0x7f3dc2dc2104 in LineLeft src/layout/generic/nsFloatManager.cpp:2348:43
#6 0x7f3dc2dc2104 in nsFloatManager::GetFlowArea(mozilla::WritingMode, int, int, nsFloatManager::BandInfoType, nsFloatManager::ShapeType, mozilla::LogicalRect, nsFloatManager::SavedState*, nsSize const&) const src/layout/generic/nsFloatManager.cpp:225
#7 0x7f3dc2cbef1e in GetFloatAvailableSpaceWithState src/layout/generic/BlockReflowInput.cpp:345:21
#8 0x7f3dc2cbef1e in GetFloatAvailableSpace src/layout/generic/BlockReflowInput.h:134
#9 0x7f3dc2cbef1e in mozilla::BlockReflowInput::AddFloat(nsLineLayout*, nsIFrame*, int) src/layout/generic/BlockReflowInput.cpp:636
#10 0x7f3dc2f1f061 in AddFloat src/layout/generic/nsLineLayout.h:182:22
#11 0x7f3dc2f1f061 in nsLineLayout::ReflowFrame(nsIFrame*, nsReflowStatus&, mozilla::ReflowOutput*, bool&) src/layout/generic/nsLineLayout.cpp:966
#12 0x7f3dc2d5073d in nsBlockFrame::ReflowInlineFrame(mozilla::BlockReflowInput&, nsLineLayout&, nsLineList_iterator, nsIFrame*, LineReflowStatus*) src/layout/generic/nsBlockFrame.cpp:4158:15
#13 0x7f3dc2d4f0e7 in nsBlockFrame::DoReflowInlineFrames(mozilla::BlockReflowInput&, nsLineLayout&, nsLineList_iterator, nsFlowAreaRect&, int&, nsFloatManager::SavedState*, bool*, LineReflowStatus*, bool) src/layout/generic/nsBlockFrame.cpp:3958:5
#14 0x7f3dc2d45e09 in nsBlockFrame::ReflowInlineFrames(mozilla::BlockReflowInput&, nsLineList_iterator, bool*) src/layout/generic/nsBlockFrame.cpp:3832:9
#15 0x7f3dc2d3e360 in nsBlockFrame::ReflowLine(mozilla::BlockReflowInput&, nsLineList_iterator, bool*) src/layout/generic/nsBlockFrame.cpp:2816:5
#16 0x7f3dc2d33be0 in nsBlockFrame::ReflowDirtyLines(mozilla::BlockReflowInput&) src/layout/generic/nsBlockFrame.cpp:2352:7
#17 0x7f3dc2d2b3f4 in nsBlockFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/generic/nsBlockFrame.cpp:1225:3
#18 0x7f3dc2d8b8b6 in nsContainerFrame::ReflowChild(nsIFrame*, nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, mozilla::WritingMode const&, mozilla::LogicalPoint const&, nsSize const&, unsigned int, nsReflowStatus&, nsOverflowContinuationTracker*) src/layout/generic/nsContainerFrame.cpp:951:14
#19 0x7f3dc303f55b in nsHTMLButtonControlFrame::ReflowButtonContents(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsIFrame*) src/layout/forms/nsHTMLButtonControlFrame.cpp:252:3
#20 0x7f3dc303ecb0 in nsHTMLButtonControlFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/forms/nsHTMLButtonControlFrame.cpp:204:3
#21 0x7f3dc2f1ec6f in nsLineLayout::ReflowFrame(nsIFrame*, nsReflowStatus&, mozilla::ReflowOutput*, bool&) src/layout/generic/nsLineLayout.cpp:924:13
#22 0x7f3dc2d5073d in nsBlockFrame::ReflowInlineFrame(mozilla::BlockReflowInput&, nsLineLayout&, nsLineList_iterator, nsIFrame*, LineReflowStatus*) src/layout/generic/nsBlockFrame.cpp:4158:15
#23 0x7f3dc2d4f0e7 in nsBlockFrame::DoReflowInlineFrames(mozilla::BlockReflowInput&, nsLineLayout&, nsLineList_iterator, nsFlowAreaRect&, int&, nsFloatManager::SavedState*, bool*, LineReflowStatus*, bool) src/layout/generic/nsBlockFrame.cpp:3958:5
#24 0x7f3dc2d45e09 in nsBlockFrame::ReflowInlineFrames(mozilla::BlockReflowInput&, nsLineList_iterator, bool*) src/layout/generic/nsBlockFrame.cpp:3832:9
#25 0x7f3dc2d3e360 in nsBlockFrame::ReflowLine(mozilla::BlockReflowInput&, nsLineList_iterator, bool*) src/layout/generic/nsBlockFrame.cpp:2816:5
#26 0x7f3dc2d33be0 in nsBlockFrame::ReflowDirtyLines(mozilla::BlockReflowInput&) src/layout/generic/nsBlockFrame.cpp:2352:7
#27 0x7f3dc2d2b3f4 in nsBlockFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/generic/nsBlockFrame.cpp:1225:3
#28 0x7f3dc2d4c667 in nsBlockReflowContext::ReflowBlock(mozilla::LogicalRect const&, bool, nsCollapsingMargin&, int, bool, nsLineBox*, mozilla::ReflowInput&, nsReflowStatus&, mozilla::BlockReflowInput&) src/layout/generic/nsBlockReflowContext.cpp:306:11
#29 0x7f3dc2d406e3 in nsBlockFrame::ReflowBlockFrame(mozilla::BlockReflowInput&, nsLineList_iterator, bool*) src/layout/generic/nsBlockFrame.cpp:3463:11
#30 0x7f3dc2d3e4b5 in nsBlockFrame::ReflowLine(mozilla::BlockReflowInput&, nsLineList_iterator, bool*) src/layout/generic/nsBlockFrame.cpp:2813:5
#31 0x7f3dc2d33be0 in nsBlockFrame::ReflowDirtyLines(mozilla::BlockReflowInput&) src/layout/generic/nsBlockFrame.cpp:2352:7
#32 0x7f3dc2d2b3f4 in nsBlockFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/generic/nsBlockFrame.cpp:1225:3
#33 0x7f3dc2d8b8b6 in nsContainerFrame::ReflowChild(nsIFrame*, nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, mozilla::WritingMode const&, mozilla::LogicalPoint const&, nsSize const&, unsigned int, nsReflowStatus&, nsOverflowContinuationTracker*) src/layout/generic/nsContainerFrame.cpp:951:14
#34 0x7f3dc2d8a102 in nsCanvasFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/generic/nsCanvasFrame.cpp:713:5
#35 0x7f3dc2d8b8b6 in nsContainerFrame::ReflowChild(nsIFrame*, nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, mozilla::WritingMode const&, mozilla::LogicalPoint const&, nsSize const&, unsigned int, nsReflowStatus&, nsOverflowContinuationTracker*) src/layout/generic/nsContainerFrame.cpp:951:14
#36 0x7f3dc2e76658 in nsHTMLScrollFrame::ReflowScrolledFrame(mozilla::ScrollReflowInput*, bool, bool, mozilla::ReflowOutput*, bool) src/layout/generic/nsGfxScrollFrame.cpp:555:3
#37 0x7f3dc2e77a79 in nsHTMLScrollFrame::ReflowContents(mozilla::ScrollReflowInput*, mozilla::ReflowOutput const&) src/layout/generic/nsGfxScrollFrame.cpp:678:3
#38 0x7f3dc2e7ba58 in nsHTMLScrollFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/generic/nsGfxScrollFrame.cpp:1055:3
#39 0x7f3dc2d0f74e in nsContainerFrame::ReflowChild(nsIFrame*, nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, int, int, unsigned int, nsReflowStatus&, nsOverflowContinuationTracker*) src/layout/generic/nsContainerFrame.cpp:995:14
#40 0x7f3dc2d0e2ce in mozilla::ViewportFrame::Reflow(nsPresContext*, mozilla::ReflowOutput&, mozilla::ReflowInput const&, nsReflowStatus&) src/layout/generic/ViewportFrame.cpp:335:7
#41 0x7f3dc2af3c10 in mozilla::PresShell::DoReflow(nsIFrame*, bool) src/layout/base/PresShell.cpp:8983:11
#42 0x7f3dc2b09b20 in mozilla::PresShell::ProcessReflowCommands(bool) src/layout/base/PresShell.cpp:9156:24
#43 0x7f3dc2b07f29 in mozilla::PresShell::DoFlushPendingNotifications(mozilla::ChangesToFlush) src/layout/base/PresShell.cpp:4366:11
#44 0x7f3dc2be5030 in FlushPendingNotifications src/obj-firefox/dist/include/nsIPresShell.h:583:5
#45 0x7f3dc2be5030 in nsDocumentViewer::LoadComplete(nsresult) src/layout/base/nsDocumentViewer.cpp:982
#46 0x7f3dc5d3f8a2 in nsDocShell::EndPageLoad(nsIWebProgress*, nsIChannel*, nsresult) src/docshell/base/nsDocShell.cpp:7236:21
#47 0x7f3dc5d3bcc9 in nsDocShell::OnStateChange(nsIWebProgress*, nsIRequest*, unsigned int, nsresult) src/docshell/base/nsDocShell.cpp:7029:7
#48 0x7f3dc5d434cf in non-virtual thunk to nsDocShell::OnStateChange(nsIWebProgress*, nsIRequest*, unsigned int, nsresult) src/docshell/base/nsDocShell.cpp
#49 0x7f3dbc9ecef7 in nsDocLoader::DoFireOnStateChange(nsIWebProgress*, nsIRequest*, int&, nsresult) src/uriloader/base/nsDocLoader.cpp:1315:3
#50 0x7f3dbc9ebf7a in nsDocLoader::doStopDocumentLoad(nsIRequest*, nsresult) src/uriloader/base/nsDocLoader.cpp:858:14
#51 0x7f3dbc9e8b55 in nsDocLoader::DocLoaderIsEmpty(bool) src/uriloader/base/nsDocLoader.cpp:747:9
#52 0x7f3dbc9eab1c in nsDocLoader::OnStopRequest(nsIRequest*, nsISupports*, nsresult) src/uriloader/base/nsDocLoader.cpp:632:5
#53 0x7f3dbc9ebb3c in non-virtual thunk to nsDocLoader::OnStopRequest(nsIRequest*, nsISupports*, nsresult) src/uriloader/base/nsDocLoader.cpp
#54 0x7f3dbae1fd1a in mozilla::net::nsLoadGroup::RemoveRequest(nsIRequest*, nsISupports*, nsresult) src/netwerk/base/nsLoadGroup.cpp:629:28
#55 0x7f3dbdda526a in DoUnblockOnload src/dom/base/nsDocument.cpp:8419:18
#56 0x7f3dbdda526a in nsDocument::UnblockOnload(bool) src/dom/base/nsDocument.cpp:8341
#57 0x7f3dbdd85bd4 in nsIDocument::DispatchContentLoadedEvents() src/dom/base/nsDocument.cpp:5321:3
#58 0x7f3dbde9cde4 in applyImpl<nsIDocument, void (nsIDocument::*)()> src/obj-firefox/dist/include/nsThreadUtils.h:1165:12
#59 0x7f3dbde9cde4 in apply<nsIDocument, void (nsIDocument::*)()> src/obj-firefox/dist/include/nsThreadUtils.h:1171
#60 0x7f3dbde9cde4 in mozilla::detail::RunnableMethodImpl<nsIDocument*, void (nsIDocument::*)(), true, (mozilla::RunnableKind)0>::Run() src/obj-firefox/dist/include/nsThreadUtils.h:1216
#61 0x7f3dbac180d1 in mozilla::SchedulerGroup::Runnable::Run() src/xpcom/threads/SchedulerGroup.cpp:337:32
#62 0x7f3dbac36ec9 in nsThread::ProcessNextEvent(bool, bool*) src/xpcom/threads/nsThread.cpp:1090:14
#63 0x7f3dbac52900 in NS_ProcessNextEvent(nsIThread*, bool) src/xpcom/threads/nsThreadUtils.cpp:519:10
#64 0x7f3dbbb306da in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) src/ipc/glue/MessagePump.cpp:97:21
#65 0x7f3dbba84f89 in RunInternal src/ipc/chromium/src/base/message_loop.cc:326:10
#66 0x7f3dbba84f89 in RunHandler src/ipc/chromium/src/base/message_loop.cc:319
#67 0x7f3dbba84f89 in MessageLoop::Run() src/ipc/chromium/src/base/message_loop.cc:299
#68 0x7f3dc253e57a in nsBaseAppShell::Run() src/widget/nsBaseAppShell.cpp:157:27
#69 0x7f3dc67b2f7b in XRE_RunAppShell() src/toolkit/xre/nsEmbedFunctions.cpp:893:22
#70 0x7f3dbba84f89 in RunInternal src/ipc/chromium/src/base/message_loop.cc:326:10
#71 0x7f3dbba84f89 in RunHandler src/ipc/chromium/src/base/message_loop.cc:319
#72 0x7f3dbba84f89 in MessageLoop::Run() src/ipc/chromium/src/base/message_loop.cc:299
#73 0x7f3dc67b2940 in XRE_InitChildProcess(int, char**, XREChildData const*) src/toolkit/xre/nsEmbedFunctions.cpp:719:34
#74 0x4f1875 in content_process_main src/browser/app/../../ipc/contentproc/plugin-container.cpp:50:30
#75 0x4f1875 in main src/browser/app/nsBrowserApp.cpp:280
#76 0x7f3dda3bc82f in __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/../csu/libc-start.c:291
#77 0x420f48 in _start (firefox+0x420f48)
|
|
1,459,760 | 13,260,978 |
Steps to reproduce:
1. Enable gfx.webrender.all
2. Go to a website that you don't have bookmarked.
3. Click the star icon at the end of the URL button.
Expected results:
The animation should look good.
Actual results:
The star flickers during the animation.
|
|
1,459,899 | 13,262,128 |
[Environment:]
Windows 8.1 x64
62.0a1 20180507222648
[Prerequisites:]
1. Set the app.normandy.dev_mode preference to true to run recipes immediately on startup.
2. Set the app.normandy.logging.level preference to 0 to enable more logging.
3. Set 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.
4. Set the preference value for app.normandy.api_url set to https://normandy.stage.mozaws.net/api/v1
[Steps:]
1. Open Control Center (https://normandy-admin.stage.mozaws.net/)
2. Create a rollout recipe with the blob:
{
"preferences": [
{
"preferenceName": "test.int.1",
"value": 1
}
],
"slug": "rollout-pref"
}
3. Save, Approve, Publish the recipe.
4. Set prerequisites and open a Firefox client which supports rollouts (Fx61+)
5. Open Browser Console and notice the logs.
6. Restart Firefox.
7. Look again at browser console.
[Actual Result:]
5.
app.normandy.recipe-runner INFO Executing recipe "Rollout exp" (action=preference-rollout)
app.normandy.action.PreferenceRolloutAction DEBUG Enrolled in preference rollout rollout-pref
7.
app.normandy.recipe-runner INFO Executing recipe "rollout-pref" (action=preference-rollout)
app.normandy.action.PreferenceRolloutAction DEBUG updating rollout-graduation1: test.int.1 previous value changed from null to 1
app.normandy.action.PreferenceRolloutAction DEBUG Updated preference rollout rollout-pref
in about:telemtry -> normandy update preference_rollout rollout-pref {"previousState": "active"}
[Expected Result:]
No update should be performed upon restart, no telemetry event should be logged either.
[Note:]
Repeating step 6 produces the same AR.
|
|
1,460,082 | 13,263,901 |
We are looking into removing the `app.update.enabled` pref, and replacing that functionality with the DisableAppUpdate and DisableSystemAddonUpdate policies. This would make it necessary to enable these policies outside of ESR builds.
|
|
1,460,119 | 13,264,220 |
See https://github.com/mozmeao/snippets-service/pull/395#issuecomment-385320405
|
|
1,460,202 | 13,264,582 |
Created attachment 8974281
FF-no-zoom.PNG
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180404120016
Steps to reproduce:
Open the link: https://www.gsmarena.com/android_p_beta_is_out_today_for_pixels-news-30932.php
Actual results:
Unlike Safari, unable to zoom into the webpage. Check attachments.
Expected results:
The webpage should be zoomable.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.