Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
β |
|---|---|---|---|
1,663,000 | 15,020,310 |
Following the discussions from Fenix - https://github.com/mozilla-mobile/fenix/issues/13797
There is an issue where pages have a height bigger than (window - toolbar) but smaller than window (ending underneath the toolbar) and so the page will not be considered as scrollble -> the dynamic toolbar won't be animated away to allow viewing / interacting with the very bottom of the page.
(Botond Ballo (:botond) from https://github.com/mozilla-mobile/fenix/issues/13797#issuecomment-685974024)
> My suggestion for how to handle this case, as mentioned, is to size the viewport to the (window - toolbar) height. The resulting behaviour would depend on the page:
> - If the page has a fixed content height (e.g. a GitHub issues list with a fixed number of issues to display) that just happens to fall into this small range, then the page would become a bit scrollable, like you said.
> - If the page has content height == viewport height, then the content height would shrink. This covers cases like the ublock settings page (where an iframe's viewport takes up the page viewport; the iframe would remain scrollable with the smaller viewport, as desired), as well as cases like a mapping or drawing application where the canvas size would simply be reduced by the height of the toolbar.
For a minimal testcase - https://codepen.io/mattok/full/XWdeQZY
|
|
1,663,273 | 15,021,961 |
Created attachment 9174063
Capture dβΓ©cran_2020-09-05_20-05-19.png
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0
Steps to reproduce:
A white band on the top of each web page (see screenshot) since yesterday afternoon 4.9.2020
On Twitter just no time line
I've wait updates: nothing have change
I've download a new Nightly: nothing have change
In these conditions impossible with my knowledge to try anything locally
|
|
1,666,687 | 15,049,314 |
Created attachment 9177291
2020-09-23_10-38.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
0. AltLinux, firefox-81.0.tar.bz2 from official site.
1. print.tab_modal.enabled pref is set to true
2. open any site
3. Ctrl-P
4. Prepair to preview.. forever..
Actual results:
print preview and nothing.. no preview, no printers, no anything, only wait cursor
p.s. in console i see
(firefox:17079): Gtk-WARNING **: Unknown paper size
(firefox:17079): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Expected results:
I want see print preview page and print it
|
|
1,668,071 | 15,059,868 |
Created attachment 9178515
CSPContent.csp.log.moz_log
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36
Steps to reproduce:
We have a content security policy with a frame-src and frame-ancestors directive, but while Chrome loads the iframe successfully, Firefox doesn't.
Here's our full CSP Policy (notice the settings for frame-ancestors):
```
frame-ancestors: *.walkmetest.apps.suite-ocp-dev.cp.fyre.ibm.com 'self'; default-src 'self'; connect-src 'self' https://*.kampyle.com https://*.ibm.com https://*.bluemix.net wss://*.ibmcloud.com https://*.medallia.eu https://*.segment.io https://admin.walkmetest.apps.suite-ocp-dev.cp.fyre.ibm.com https://*.braze.com; script-src 'self' https://*.kampyle.com https://*.ibm.com https://*.bluemix.net https://*.braze.com https://*.medallia.eu https://*.lpsnmedia.net https://*.segment.com https://*.truste.com https://*.trustarc.com https://admin.walkmetest.apps.suite-ocp-dev.cp.fyre.ibm.com 'unsafe-eval' 'unsafe-inline'; img-src 'self' data: blob: https://*.kampyle.com https://*.ibm.com https://*.walkmeusercontent.com https://*.cloudfront.net; style-src 'self' 'unsafe-inline' blob: https://*.ibm.com; font-src 'self' https://fonts.gstatic.com https://*.ibm.com data: https://1.www.s81c.com https://*.medallia.eu https://*.s81c.com; frame-src 'self' https://*.trustarc.com https://*.truste.com https://admin.walkmetest.apps.suite-ocp-dev.cp.fyre.ibm.com;
```
Actual results:
I turned up debugging to show the CSPContext logs from Firefox when trying to determine whether this page should load or not and have it attached in the log
If I turn off the frame-ancestors setting (and X-Frame-Options) entirely the frame loads fine, but this of course causes a security hole in our app, so I would like to prevent this.
Expected results:
I believe the frame should have loaded successfully with these frame-ancestors. Instead it shows the error page for about:blank with an CSP error highlighed
I'm also seeing this in the logs
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
CDhiddenIframe.compress.html
This error page has no error code in its security info aboutNetError.js:585:13
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
dashboardpins
|
|
1,668,371 | 15,061,706 |
Occasionally, the general uploads page is slow:
https://symbols.mozilla.org/uploads
Much more often, the upload files page is slow:
https://symbols.mozilla.org/uploads/files/
This bug covers getting timings, figuring out what the issues are, and then fixing them.
|
|
1,668,492 | 15,062,676 |
[Spinning this off from bug 1668002 comment 13.]
The code for saving print settings as float prefs is locale aware, but the code for reading those same prefs is not:
https://searchfox.org/mozilla-central/rev/f21850ca45036ddb84cd25aa355a6969d7c94c4f/widget/nsPrintSettingsService.cpp#1007-1027
Specifically, nsPrintfCString is locale aware by virtue of it using nsTSubstring::AppendPrintf [which is locale aware](https://searchfox.org/mozilla-central/rev/f21850ca45036ddb84cd25aa355a6969d7c94c4f/xpcom/string/nsTSubstring.h#636-641,643). However, `atof` is not locale aware and will stop parsing when it encounters a decimal separator that is not ".". In practice this means that for affected users pref values essentially undergo a floor() conversion on being read. So:
```
print_paper_height: 11,69 -> 11
print_paper_width: 8,27 -> 8
print_scaling: 1,50 -> 1
```
You'd think after 20 years we'd have noticed this bug, but I guess not. Other than the fact that the printing code has been unowned and 1000+ bug reports remain open, I guess this is because most users with a locale that uses a decimal separator other than "." probably use paper sizes in millimeters rather than inches, and paper sizes in millimeters don't tend to have a decimal component. Also I guess maybe this bug only causes some misscaling (resolution?) issues in the common case?
|
|
1,669,063 | 15,066,638 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
Looking different e-mails in the preview window.
Actual results:
Hello everybody,
with Thunderbird 78 there is no right-clickable
customize function in the preview window, as you can see in
Thunderbird 68. So you can also get there from Extensions (=
Add-ons) such as "Allow HTML Temp" or "Display
Mail User Agent" added buttons not hide or remove.
This has the consequence that the preview window simply opens on
the right is cut off, which has or have different consequences
can:
a) The last switch on the right outer position will may be cut off
or disappear into the non visible area.
b) The date/time display of the e-mail is cut off or may disappear
completely into the non-visible area.
c) Mailtext is displayed, provided that the visible area of the
preview window, also cut off on the right.
The complete readability of an e-mail itself and the Header data
is only possible if the e-mail is sent by double-clicking will
open in a separate window.
In the German forum Thunderbird Mail DE you can find the
following Thread:
https://www.thunderbird-mail.de/forum/thread/85413-thunderbird-78-
vorschaufenster-wird-teilweise-rechts-abgeschnitten/
Sorry for my English. Translated from German with DeepL
Expected results:
If it is all well, then it should be none "cut off" on the right side.
|
|
1,669,390 | 15,069,960 |
Bug 1662222 changed the `settingsAreComplete` variable so that we include invocations by extensions which tend to be where our silent prints come from. That means we don't enter the block of code that tracks silent prints in early-beta-and-earlier where the pref is on by default..
https://searchfox.org/mozilla-central/rev/35245411b9e8a911fe3f5adb0632c3394f8b4ccb/layout/printing/nsPrintJob.cpp#642-648,653,663-665
FWIW, the telemetry code was originally written that way to avoid counting silent prints in the two "dialog opened" probes.
|
|
1,666,176 | 15,045,742 |
Null pointer crash at gfxPlatform::Init()
bt: https://crash-stats.mozilla.org/report/index/d6d0d74f-ff27-4377-89b8-6f7c00200920
|
|
1,630,380 | 14,757,609 |
Created attachment 9140855
highlighted-empty-username.png
Highlighting input elements when they are autofilled is used to communicate to the user that we have made a change to it. When the saved login username is blank, we are not making any change to the element, so highlighting it is confusing. In the worst case users might (erroneously) believe that we have blanked the field.
Steps to reproduce:
- On any site we are capable of autofilling on
- Save a login with a password, but with an empty username field
- Refresh page
Expected:
- Password field is filled in and higlighted
- Username field is unchanged
Actual:
- Password field is filled in and highlighted
- Username field is highlighted
|
|
1,631,281 | 14,763,787 |
Created attachment 9141552
8xxnzpbmnpt41.jpg
From: https://www.reddit.com/r/firefox/comments/g42asi/when_disabling_switch_to_tab_feature_on_address/
Steps to reproduce:
1. Ensure YouTube is in top sites
2. Open YouTube
3. Ensure "Open tabs" suggestion is disabled for address bar
4. open new tab, navigate to any other site
5. Click on address bar
What happens:
YouTube doesn't appear in the top sites suggestions in the address bar.
Expected result:
YouTube appears; clicking the suggestion opens it without switching to existing tab.
|
|
1,631,799 | 14,769,056 |
**Steps to reproduce**
1. In about:debugging select a device with GeckoView running
1. In the console, evaluate a simple command (`1 + 1`)
**Expected results**
The result (`2`) is displayed __after__ the command (`1 + 1`)
**Actual results**
it might happen that the result is displayed __before__ the command.
This is because the command timeStamp is set on the client, although the result timestamp is set on the server, and the remote device might have a different clock than the one you're using to debug.
And since we now rely on the timeStamps to sort the messages, we have an issue.
---
We could fix this for the result only (we could check the result timestamp, and if it's before the command, change it to be the command timestamp + x, but we would have a wrong order anyway if the command emit some logs).
|
|
1,632,786 | 14,775,932 |
Created attachment 9143013
canceling the OS auth dialog is counted as invalid login.gif
[Affected versions]:
- Nightly 77.0a1;
- Beta 76.0b8;
[Affected Platforms]:
- Windows 10 x64;
- Windows 7 x64;
- Windows 8.1 x32;
[Prerequisites]:
- Have an OS password set.
- Have at least one login saved.
- Have an account lockout policy set to 5 invalid logon attempts.
[Steps to reproduce]:
1. Open the latest Nightly Firefox browser.
2. Navigate to the "about:logins" page and select a saved login.
3. Click on the "Show Password" button.
4. Click the "Cancel" button of the OS auth dialog.
5. Repeat 4 more times the step 3 and 4.
6. Click again the "Show Password" button.
7. In the OS auth dialog enter the valid password.
8. Observe the behavior.
[Expected result]:
- The password is shown.
[Actual result]:
- "The referenced account is currently locked out and may not be logged on to." message is displayed and the password is not shown.
[Notes]:
- Also, the "`pwmgr reauthenticate os_auth fail`" telemetry event is registered when the OS auth dialog is canceled. This telemetry event is also sent on Mac OS when the auth dialog is canceled.
- Attached a screen recording with the issue.
|
|
1,636,568 | 14,805,428 |
Since the Firefox 76 launch our Sentry server has been receiving a very large (1M+) number of error messages.
This comes from a code path that was mostly quiet and seemingly does not keep Screenshots from working, but was reporting errors so we could debug the exceptions. This has clearly gotten out of control.
I looked into suppressing Sentry generally in the client, which we should consider, but we can also suppress this particular exception fairly easily. The error is in [uicontrol.js](https://searchfox.org/mozilla-central/rev/dc4560dcaafd79375b9411fdbbaaebb0a59a93ac/browser/extensions/screenshots/selector/uicontrol.js#455-461)
|
|
1,633,103 | 14,777,850 |
Created attachment 9143319
screencast_of_the_issue.mov
Nightly: 77.0a1 (2020-04-24) (64-Bit)
macOS: 10.15.4
Steps to reproduce:
1.) Enable the default setting in System Preference "Show Scrollbar automatically based on moused or trackpad"
2.) Open a page where you can scroll
3) Scroll a bit down so that scrollbar appears during scroll and disappears again when scrolling stops
4) Now scroll to the very top again
Actual: The scrollbar does not disappear again.
Expected: When you reach the very top/left/right or bottom of the page, the scrollbar should disappear again.
This is a regression at least in recent Nightly.
This is not reproducible in Firefox Stable 75.
A screencast of the issue is attached.
Thanks for fixing it in advance!
|
|
1,633,119 | 14,777,939 |
Created attachment 9143340
testcase
Steps to reproduce:
1. open the attached testcase
2. click the button "Open Window"
3. click the green full screen button on the top left corner of the new window
Expected result:
the address bar should be on the top of the screen
Actual result:
there is a grey bar, seemingly a fake title bar
|
|
1,633,204 | 14,778,365 |
This bug is for crash report bp-1e806b21-7b43-4a30-ad7f-d09030200425.
```
Top 10 frames of crashing thread:
0 xul.dll static js::ObjectGroup::lazySingletonGroup js/src/vm/ObjectGroup.cpp:648
1 @0x2bac172efff
2 xul.dll XPCWrappedNativeProto::Init js/xpconnect/src/XPCWrappedNativeProto.cpp:56
3 xul.dll static XPCWrappedNativeProto::GetNewOrUsed js/xpconnect/src/XPCWrappedNativeProto.cpp:121
4 xul.dll static XPCWrappedNative::GetNewOrUsed js/xpconnect/src/XPCWrappedNative.cpp:405
5 xul.dll static XPCConvert::NativeData2JS js/xpconnect/src/XPCConvert.cpp:368
6 xul.dll nsXPCWrappedJS::CallMethod js/xpconnect/src/XPCWrappedJSClass.cpp:916
7 xul.dll PrepareAndDispatch xpcom/reflect/xptcall/md/win32/xptcstubs_x86_64.cpp:181
8 xul.dll SharedStub
9 xul.dll nsDocShell::InternalLoad docshell/base/nsDocShell.cpp:8808
```
New crash spike in Nightly starting with build 20200425094923
Changelog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=db2e1d780268ab0a7dca1ea1ca81febcb33e926e&tochange=d8a8178627c4fab05f1eb46ee40f55db207c7c18
|
|
1,634,153 | 14,786,983 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
Steps to reproduce:
Probably just skip to the fiddle here:
https://jsfiddle.net/xya79cqL/
Summary of the repro:
1. Scroll a textarea out of view
2. Call el.focus({preventScroll: true}) where el is an HTMLTextareaElement
3. Page scrolls even though it shouldn't.
Other notes:
* Nightly is affected
* It works correctly for <input>
* I haven't tested any other kinds of elements.
* Chrome does this correctly.
Actual results:
Page scrolls.
Expected results:
Page should not have scrolled.
|
|
1,634,404 | 14,788,700 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Steps to reproduce:
Set layout.css.devPixelsPerPx to value different than 1 or -1.
Actual results:
The menus are misplaced
Expected results:
The menus shouldn't be misplaced
|
|
1,629,835 | 14,753,826 |
In https://phabricator.services.mozilla.com/D65598 we made it so that GPU cache updates are done on as small a region as possible rather than uploading the entire row. This has the unintended consequence of making it so that uploads no longer take the fast path.
Here is a profile scrolling through hacker news comments on a Pixel 2: https://perfht.ml/2K61Ht8
Note that the implementation of `TextureUploader::upload()` already ensures that the `stride`, and `offset` within the PBO are correctly aligned. So I believe the issue is that `rect.x` is incorrectly aligned. Previously it was always zero because the entire row was uploaded. And for texture cache updates it happens to be aligned because of our allocation algorithm. So until now we haven't required code to ensure the `x` offset is correct.
|
|
377,621 | 3,161,448 |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.3) Gecko/20060601 Firefox/2.0.0.3 (Ubuntu-edgy)
Build Identifier: Thunderbird Version 2.0.0.0 (20070326) and also Version 1.5.0.10 (20070306)
If you try to move a attachment via Drag and Drop outside Thunderbird to the desktop or a folder on the PC the drag and drop cursor symbols shows up correctly but no file will be created/moved to this place (This works fine under windows)
(The error shows under Gnome Desktop Ubuntu EdgyEft 6.10 and also under Feisty Fawn 7.04)
Reproducible: Always
Steps to Reproduce:
1. drag an email attachment
2. move the cursor to desktop (press shift or control or nothing - same thing)
3. release mouse button
Actual Results:
no file will be created/moved to the drop place
Expected Results:
the attachment should moved/copied to the drop place (in windows this works fine)
|
|
1,810,797 | 16,239,552 |
Kubuntu 22.04, current Nightly, X11 (not Wayland), NVIDIA drivers (This is AFAIK the current default on Kubuntu LTS)
1) Open a Firefox Window.
2) Expand the downloads panel.
3) Minimize
The downloads panel stays visible, obscuring whatever else is on screen now.
This is a recent regression.
|
|
1,801,024 | 16,162,329 |
I'm seeing logs with:
> Sync.Telemetry ERROR Notification for engine tabs but it isn't current
So the telemetry module doesn't think the tab engine is currently syncing when it is - [see here](https://searchfox.org/mozilla-central/source/services/sync/modules/telemetry.js#641)
This message also causes an error log to be recorded. I haven't dug into the implications of this.
|
|
1,812,771 | 16,253,330 |
From github: https://github.com/mozilla-mobile/fenix/issues/23977.
> ### Steps to reproduce
>
> More than half of the [Socorro crash reports from Fenix or Focus](https://crash-stats.mozilla.org/search/?product=Focus&date=%3E%3D2022-02-17T19%3A55%3A00.000Z&date=%3C2022-02-24T19%3A55%3A00.000Z&_facets=signature&_facets=build_id&_facets=product&_facets=release_channel&_facets=platform&_facets=platform_pretty_version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-platform) have "Platform" == "Unknown" instead of "Android".
>
> The [Socorro crash reports with Platform == "Android"](https://crash-stats.mozilla.org/search/?product=Focus&platform=Android&date=%3E%3D2022-02-17T19%3A55%3A00.000Z&date=%3C2022-02-24T19%3A55%3A00.000Z&_facets=signature&_facets=build_id&_facets=product&_facets=release_channel&_facets=platform&_facets=platform_pretty_version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature) are all native code crashes.
>
> The [Socorro crash reports with Platform == "Unknown"](https://crash-stats.mozilla.org/search/?product=Focus&platform=Unknown&date=%3E%3D2022-02-17T19%3A55%3A00.000Z&date=%3C2022-02-24T19%3A55%3A00.000Z&_facets=signature&_facets=build_id&_facets=product&_facets=release_channel&_facets=platform&_facets=platform_pretty_version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature) are all Java exceptions.
>
> ### Expected behaviour
>
> All Socorro crash reports from Fenix or Focus should have "Platform" == "Android".
>
> ### Actual behaviour
>
> Socorro crash reports for Java exceptions from Fenix or Focus have "Platform" == "Unknown".
>
> ### Device name
>
> _No response_
>
> ### Android version
>
> Android 10
>
> ### Firefox release type
>
> Firefox
>
> ### Firefox version
>
> 97.0
>
> ### Device logs
>
> _No response_
>
> ### Additional information
>
> _No response_
>
> βIssue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FNXV2-19650)
>
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,808,962 | 16,225,152 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
In Ubuntu 22.02 (Wayland) and Firefox 108 (though I believe this issue was introduced in Firefox 106) if the date picker is low on the screen (where there is not enough space below the date field for the picker to display) then it doesn't show at all.
If you go to this page there is a date field with the date (6/1/17) in the box:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date
If you click in the date field input when the date field is higher up the screen then the date picker is launched and you can select a date from it.
If you scroll so that the date picker is near the bottom of the screen and click inside the date field input then the date picker does not display.
Actual results:
The date picker does not display.
Expected results:
The date picker should open above the date field input.
|
|
1,758,566 | 15,805,090 |
The symbols from [this try job](https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=cccfb7dd33b48a1419826a889a18eff916906fec&searchStr=win&selectedTaskRun=PJp4e73mRIWRAyXyTDjEOQ.0) don't seem to have made it to the symbol server. For example, the log contains:
```
[task 2022-03-08T19:37:00.768Z] INFO:upload-symbols:firefox.pdb/192BF8D55EFAFBE74C4C44205044422E1/firefox.pdb
[task 2022-03-08T19:37:01.435Z] INFO:upload-symbols:firefox.pdb/192BF8D55EFAFBE74C4C44205044422E1/firefox.sym
...
[task 2022-03-08T19:43:01.560Z] INFO:upload-symbols:Using symbol upload token from the secrets service: "http://taskcluster/secrets/v1/secret/project/releng/gecko/build/level-1/gecko-symbol-upload"
[task 2022-03-08T19:43:01.645Z] INFO:upload-symbols:Uploading symbol file "/tmp/tmpfkr2qj7_/symbols.zip" to "https://symbols.mozilla.org/upload/"
[task 2022-03-08T19:43:01.645Z] INFO:upload-symbols:Attempt 1 of 7...
[task 2022-03-08T19:44:23.053Z] INFO:upload-symbols:Uploaded successfully!
```
However, the uploaded firefox.sym file is not available:
https://symbols.mozilla.org/firefox.pdb/192BF8D55EFAFBE74C4C44205044422E1/firefox.sym
And the profiler's request to the symbolication API also doesn't succeed.
```
curl --compressed 'https://symbolication.services.mozilla.com/symbolicate/v5' -d '{"jobs":[{"memoryMap":[["firefox.pdb","192BF8D55EFAFBE74C4C44205044422E1"]],"stacks":[[[0, 384823]]]}]}'
```
```json
{
"results": [
{
"stacks": [
[
{
"frame": 0,
"module": "firefox.pdb",
"module_offset": "0x5df37"
}
]
],
"found_modules": {
"firefox.pdb/192BF8D55EFAFBE74C4C44205044422E1": false
}
}
]
}
```
|
|
1,750,017 | 15,731,752 |
Reproduction: start Firefox Nightly in a clean profile. Open a second window with Ctrl-N. Grab the titlebar and move the second window to become a tab in the first one. Firefox Nightly dumps core. I am using fvwm on 64-bit Fedora 34 on Intel integrated graphics (i7-8700K) on a 4k display.
Mozregression narrows this to https://hg.mozilla.org/integration/autoland/rev/841415a89add828287f52888deab7c107316f095, which is a commit for bug 1743821 that changes when things are released.
|
|
1,753,002 | 15,757,529 | null |
|
1,746,254 | 15,699,166 |
See this try push: https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=8dc0a26989e2ed28b3b8ec5897f62d8533c5b77d
|
|
1,732,682 | 15,586,758 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:92.0) Gecko/20100101 Firefox/92.0
Steps to reproduce:
With the new nightly builds, the popup menus are cut off in KDE/Wayland with HiDPI monitor. The issues was resolved in #1718507, but it showed up again in the new nightly build.
Here is the result from mozregression.
5:44.33 INFO: Narrowed integration regression window from [cd6051c0, 3b856ecc] (3 builds) to [0850c74d, 3b856ecc] (2 builds) (~1 steps left)
5:44.33 INFO: No more integration revisions, bisection finished.
5:44.33 INFO: Last good revision: 0850c74da42fb3c1568b5d4fb49c2b1d2786eedb
5:44.33 INFO: First bad revision: 3b856ecc00e4b07744f6c68c7ba851ca05944025
5:44.33 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0850c74da42fb3c1568b5d4fb49c2b1d2786eedb&tochange=3b856ecc00e4b07744f6c68c7ba851ca05944025
Here is the log with MOZ_LOG="WidgetScreen:5"
[Parent 742476: Main Thread]: D/WidgetScreen ScreenGetterGtk created
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing screens
[Parent 742476: Main Thread]: D/WidgetScreen GDK reports 1 screens
[Parent 742476: Main Thread]: D/WidgetScreen New screen [0 0 1920 1080 (0 0 1920 1080) 32 2.000000 2.000000 80.682350]
[Parent 742476: Main Thread]: D/WidgetScreen Refresh screens
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing all ContentParents
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742634]
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: D/WidgetScreen Received monitors-changed event
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing screens
[Parent 742476: Main Thread]: D/WidgetScreen GDK reports 1 screens
[Parent 742476: Main Thread]: D/WidgetScreen New screen [0 0 1920 1080 (0 0 1920 1080) 32 2.000000 2.000000 80.682350]
[Parent 742476: Main Thread]: D/WidgetScreen Refresh screens
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing all ContentParents
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742634]
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742690]
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: D/WidgetScreen Received monitors-changed event
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing screens
[Parent 742476: Main Thread]: D/WidgetScreen GDK reports 1 screens
[Parent 742476: Main Thread]: D/WidgetScreen New screen [0 0 1920 1080 (0 0 1920 1080) 32 2.000000 2.000000 80.682350]
[Parent 742476: Main Thread]: D/WidgetScreen Refresh screens
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing all ContentParents
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742634]
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742690]
[Child 742634: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742634: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Child 742690: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742828]
[Parent 742476: Main Thread]: D/WidgetScreen Received monitors-changed event
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing screens
[Parent 742476: Main Thread]: D/WidgetScreen GDK reports 1 screens
[Parent 742476: Main Thread]: D/WidgetScreen New screen [0 0 1920 1080 (0 0 1920 1080) 32 2.000000 2.000000 80.682350]
[Parent 742476: Main Thread]: D/WidgetScreen Refresh screens
[Parent 742476: Main Thread]: D/WidgetScreen Refreshing all ContentParents
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742634]
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742690]
[Parent 742476: Main Thread]: D/WidgetScreen Send screens to [Pid 742828]
[Child 742634: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Child 742690: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Child 742828: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Child 742828: Main Thread]: D/WidgetScreen Refresh screens from IPC
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[Parent 742476: Main Thread]: W/WidgetScreen Getting screen in wayland, primary display will be returned.
[2021-09-19T00:41:32Z ERROR xulstore::persist] removeDocument error: unavailable
###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
|
|
1,733,754 | 15,594,096 |
Created attachment 9244056
Screenshot_KDE.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:92.0) Gecko/20100101 Firefox/92.0
Steps to reproduce:
Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
1. Run `MOZ_ENABLE_WAYLAND=1 ./firefox -ProfileManager -no-remote`
2. Install [YouTube High Definition](https://addons.mozilla.org/en-US/firefox/addon/youtube-high-definition/), [Tab Session Manager](https://addons.mozilla.org/en-US/firefox/addon/tab-session-manager), [Simple Translate](https://addons.mozilla.org/en-US/firefox/addon/simple-translate/), or [User-Agent Switcher and Manager] (https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher/)
3. Click these add-ons on the toolbar and check their dropdown list.
Actual results:
GNOME: The dropdown menu is not displayed.
KDE Plasma: The dropdown menu is displayed in the wrong position.
Expected results:
The dropdown menu will appear the same as when the window protocol is xwayland.
|
|
1,730,476 | 15,567,306 |
Use wl_output screen getter workaround on Gnome/mutter only as it causes issues to Sway compositor (https://github.com/swaywm/sway/issues/6426)
|
|
1,736,949 | 15,622,628 |
Prior to [this patch](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c0e719d876173a56b16e89b64ef3eb536f352467&tochange=20bebe9b0129b66ac814330deb5bf7d1d8aabcdc), notification popups opened in the top right corner of the screen in en-us build. Now they open in the top left corner.
STR:
1. Go to any website that isn't an internal page
2. Take a screenshot (ctrl + shift + s)
3. Click on "Copy"
|
|
1,738,542 | 15,635,119 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
use ff
Actual results:
there is a grey area in the application bar where the button should be present. Only by hovering a whitish circle appears not even a clue about the functionality
Expected results:
Just the colored buttons that should be visible there should be there.
|
|
1,738,729 | 15,637,924 |
mGdkWindow can be null so we need to handle it.
|
|
1,725,930 | 15,530,052 |
https://searchfox.org/mozilla-central/rev/d3683dbb252506400c71256ef3994cdbdfb71ada/editor/spellchecker/TextServicesDocument.cpp#1592-1593
```
bool TextServicesDocument::HasSameBlockNodeParent(Text& aTextNode1,
Text& aTextNode2) {
nsIContent* container1 = aTextNode1.GetParent();
nsIContent* container2 = aTextNode1.GetParent();
```
Could be a cause of bug 1721801, but not sure.
|
|
1,740,159 | 15,648,799 |
Created attachment 9249910
System Information
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
Since the recent upgrade to Firefox 94.0+linuxmint1+tricia, I can no longer copy directly from KeePass2 and paste into user/email and password entry fields in Firefox.
The previously installed Firefox 93.0+linuxmint1+tricia worked correctly, and I can still copy and paste to the equivalent fields in the Google Chrome browser.
I can copy the email/user name and password values from KeePass2 and paste into a text editor (eg. xed), then (re)copy those from the editor and successfully paste into (the new) Firefox.
Actual results:
Use Firefox to browse to a site that requires a user login (eg. https://bugzilla.mozilla.org/home and click "Log In". Switch to KeePass password manager, select the entry for the site whose credentials are required and copy the username or the password. Switch to Firefox and attempt to paste the value into the corresponding field. Neither ^V or right-click->paste in the field will paste the copied value.
Previous Firefox releases (up to and including 93.0+linuxmint1+tricia) permitted usernames and passwords to be copied directly using the above proceedure.
Note that I can copy the username and password values from KeePass and paste them into a text editor (eg. xed), and I can then (re)copy the value from there and successfully paste the (re-copied) value into Firefox. I can also copy the values from KeePass and paste them directly into the corresponding fields if I use the Google Chrome browser instead of Firefox.
Expected results:
Usernames and passwords should be able to be copied from KeePass and pasted directly into Firefox entry fields.
|
|
1,742,229 | 15,664,617 |
Created attachment 9251739
use-modifiers-for-yuv.patch
Steps to reproduce:
I'm attempting to get Firefox working with my new VA-API implementation that uses NVIDIA's NVDecode.
Actual results:
I just got a green box instead of the video.
Expected results:
The video should have shown.
I managed to fix the issue by getting Firefox to set the modifiers for YUV surfaces aswell as for RGBA surfaces. I've attached a patch.
|
|
1,735,095 | 15,605,170 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
- Enable Wayland using: `export MOZ_ENABLE_WAYLAND=1`
- In about:config, set `layout.css.devPixelsPerPx=1.2`
Actual results:
Popup menu flickers (for all add-ons, as well as for the Firefox settings/hamburger button).
Expected results:
According to bug 1708709, Firefox 93 should contain a fix for this flickering menu issue.
|
|
1,791,417 | 16,080,392 |
Steps to reproduce:
1. Select the URL in Firefox address bar
2. Press Ctrl+C or choose "Copy" in context menu
3. Try pasting in another app
This issue is confirmed to occur on both Mir and Weston.
Mir bug report here https://github.com/MirServer/mir/issues/2583
Actual results:
I can copy/paste URLs within Firefox, but the contents of the clipboard are not accessible from other applications.
Expected results:
Links should be pasteable into other applications.
|
|
1,791,856 | 16,083,677 |
Created attachment 9295638
2022-09-21 22-11-06.mkv
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0
Steps to reproduce:
1. Press right mouse button
2. Move cursor over menu
Actual results:
Menu disappear.
Expected results:
Menu does not disappear.
Additional info:
Operating System: Arch Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.9-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD VEGAM
Don't mind weird cursor on screen recording. On real screen it is where it should be, but on recording it is higher for some reason.
|
|
1,792,512 | 16,090,094 |
Confirmed with mozregression it was regressed by bug 1786588 patch. Tested on Firefox Wayland under KDE Plasma.
STR:
1. Open Browser Console and run `window.resizeTo(500, 500)`. Window will be resized to 500px width and 500px height.
2. Perform a **manual** resize of Firefox window (move mouse to border until cursor turns to bidirectional arrow, then drag a bit to the side).
3. Repeat step 1.
Expected:
Window should resize again to 500px width and 500px height.
Actual result:
Nothing happens. If you try without repeating values it works. For example, if you used `500, 500` in step 1, you can now run `200, 200` and it will work, only the last value is blocked. After running `200, 200`, now you can run `500, 500` again because it's no longer the value from last `resizeTo` execution.
Important:
Do not run `window.resizeTo` in step 2. Step 2 must be a manual resize.
|
|
1,792,568 | 16,090,462 |
For the last 3 days, occasionally the hamburger menu popup shows partially and after some time becomes full.
Although it doesn't happen 100% of the times, I don't recall ever seeing it happening before.
Screenshots to follow
mozregression GUI doesn't run on my system (Bug 1749215)
_Ubuntu 22.04 Wayland_
|
|
1,789,956 | 16,067,693 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0
Steps to reproduce:
I started Firefox Nightly 106.0a1 (2022-9-8) 20220908213354 on Wayland with WebRender compositing in Plasma 5.25.5 in a Fedora 37 KDE Plasma installation. I clicked on Bookmarks in the Menu bar. I moved the cursor over various bookmarks folders some of which had folders within them.
Actual results:
The contents of bookmarks folders within folders were moved to the left by about the width of a bookmark folder menu, and so they were shown over top of the folder with Firefox Nightly 106.0a1 (2022-9-8) 20220908213354. The bookmarks folders' contents stopped being shown after moving the cursor over a few folders within folders. The contents of different tabs stopped being shown correctly sometimes when trying to switch between tabs in the tab bar after the bookmarks folder's contents stopped appearing.
This problem didn't happen with 106.0a1 (2022-9-8) 20220908092810 or earlier. I ran
mozregression --good 2022-09-07 --bad 20220908213354 -p ~/.mozilla/firefox/z8d4nvrc.default-nightly --profile-persistence reuse
8:41.26 INFO: No more integration revisions, bisection finished.
8:41.26 INFO: Last good revision: 2134d24b6f1685be245cf37db75736e1b78da481 8:41.26 INFO: First bad revision: 34c74cef1af0f07a45178923456153544ca4621e
8:41.26 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2134d24b6f1685be245cf37db75736e1b78da481&tochange=34c74cef1af0f07a45178923456153544ca4621e
The bisection gave the first bad change as that for Bug 1788910 involving Wayland tooltips and popups.
34c74cef1af0f07a45178923456153544ca4621e stransky β Bug 1788910 [Wayland] Look for parents recursively at nsWindow::WaylandGetParentPosition() r=emilio
Expected results:
The contents of bookmarks folders within folders would appear normally to the right of the folders they're in. The contents of bookmarks folders would continue being shown normally. Switching between tabs would show the correct tab's screen normally after the contents of some bookmarks folders in folders were shown.
|
|
1,780,549 | 15,994,284 |
Steps to reproduce:
1. set thunderbird to offline mode
2. right click on a folder (in my case, IMAP)
3. --> properties
4. --> repair
Actual results:
The folder is emptied. All messages are gone. On the hard disk, the msf file is updated, and the corresponding mbox file is deleted
Expected results:
the msf file shoud be rebuild, but no messages should be deleted!)
My thunderbird version:
Allgemeine Informationen
Name: Thunderbird
Version: 102.0.3
Build-ID: 20220718182443
Distributions-ID:
Update-Kanal: release
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.0.3
Betriebssystem: Windows_NT 10.0 19044
Betriebssystem-Theme:
Starter-Prozess: Aktiviert
Fenster mit mehreren Prozessen: 0/0
Fission-Fenster: 0/0
StandardmΓ€Γig aktiviert
Externe Prozesse: 2
Unternehmensrichtlinien: Inaktiv
Google-Location-Service-SchlΓΌssel: Fehlt
Google-Safebrowsing-SchlΓΌssel: Fehlt
Mozilla-Location-Service-SchlΓΌssel: Fehlt
Abgesicherter Modus: false
SpeichergrΓΆΓe (RAM): 4,0 GB
Speicherplatz verfΓΌgbar: 30,3 GB
|
|
1,707,996 | 15,383,317 |
Created attachment 9218733
oh-no-the-checkbox-is-slightly-off.png
Windows that are supposed to have a native checkbox (download window, import wizard) currently look like in-content checkboxes (see attached picture).
I could only test this on mac, but it could also be an issue on other platforms.
|
|
1,708,222 | 15,384,934 |
Created attachment 9218970
scroll.png
After the font size reduction a scrollbar can still be seen on app menu at 768 heigh resolution.
The solution seem to be to reduce padding on top section of the app menu (FxA).
|
|
1,708,334 | 15,385,707 |
Created attachment 9219104
FindBar.jpg
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
1. enable mac system dark mode (?)
2. install this theme https://addons.mozilla.org/zh-TW/firefox/addon/miku-hatsune-omega-clean/
3. `cmd + f` to search text in some page
Actual results:
You have black text on black background in find bar, make it completely unusable.
Expected results:
The find bar should have a light background (as it used to be).
Or the text should be forced to be white (so you can see text).
|
|
1,709,161 | 15,392,381 |
The padding being applied to the zoom out button here:
https://searchfox.org/mozilla-central/rev/54097530955a98c768f2aaf56925578ec886ec77/browser/themes/shared/customizableui/panelUI.inc.css#1498-1500
is compacting it a bit, and getting rid of a subpixel stroke line, which makes it seem vertically off-center. It's also out of vertical alignment with the zoom in button.
I think we can achieve a match with the zoom in button by setting all padding to `0` (except maybe setting `padding-bottom: 1px` might help make it match the alignment on the zoom in button.
|
|
1,709,647 | 15,395,798 |
Created attachment 9220398
Screenshot_20210505_190535.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
Use a GTK theme (I use Materia GTK) and select a text.
Actual results:
The highlight color is a dark color on top of a black text, which makes it hard to see on dark themed websites.
|
|
1,720,551 | 15,485,534 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
* Start firefox in Arabic (right to left layout)
* Click the Application Menu button, or on a button of an extension that displays a menu.
Actual results:
Menu is not displayed. Sometimes the whole Firefox crashes.
Additional Details:
* It worked for a while, but once it started crashing it became 100% reproducible.
* This was tested on a fresh installation of Ubuntu 21.04, as well as a non-fresh installation of Pop OS 21.04, in Wayland session for both.
* Removing the entire ~/.mozilla folder does not help. Reinstalling firefox also does not help.
* Switching the language to English by simply running `LANG=en firefox` solves the issue.
* Switching to X11 seems to fix the issue as well.
Expected results:
Should work and display the menu correctly.
|
|
1,713,775 | 15,428,416 |
As seen on bug 1693004 Marionette inappropriately passes-through unknown capabilities and their values. That means in case of `webSocketUrl` not being support the value `true` will be returned. Whereby the WebDriver BiDi spec requires a string containing the host and port of the WebSocket server.
We should try to get this patch landed as soon as possible and uplift to beta (90).
|
|
1,714,586 | 15,434,199 |
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
I delete ~./cache/thunderbind and ~/.thunderbird. Then I start TB90b1. It offers me to setup an account, I do not setup account. I go in the Calendar tab. On the left there is a + for new calendars, but that + cannot be clicked. The FileβNew menu shows a βCalendarβ¦β entry, but the entry is disabled.
In the βHomeβ screen βChoose to Setupβ when I click on βCalendarβ I cen set up a calendar. I go for βOn the Networkβ calendar. As location I type cal.aegee.org, without username. I check βThis location doesnβt require credentialsβ. and βOffline supportβ.
The calendars get discovered, and the events do appear in the calendar. However the βCalendar +β tab on the left does not show any calendars. The βEvents in the next 31β days also shows nothing. The Day, Multiweek and Month views cannot be clicked, only the Week view is visible by default.
Expected results:
The discovered calendas shall be displayed on the left panel.
The βEvents in the next 31 daysβ should be displayed.
The < and > buttons (left and right from βTodayβ shall be clickable, but are not.
The buttons βDayβ, βMultiweekβ and βMonthβ on the right shall be clickable.
The + (add new calendars) button after the βCalendarβ text should be clickable.
The File β New β Calendarβ¦ menu shall be enabled.
|
|
1,718,867 | 15,470,869 |
### Steps to reproduce
Do the following, once with and once without `MOZ_ENABLE_WAYLAND=1`:
1. Shrink the window lengthways so the width is narrow (less than the width of a notification popup).
2. Move the window to the right hand side.
3. Go to `about:addons` and start to install an addon.
You should see the installation and confirmation popups.
### Result
When xwayland is in use, the notification popup extends to the left of its anchor, such that the notification is fully visible.
When wayland is in use, the notification popup still extends to the right of its anchor, such that the notification is cut off by the edge of the screen.
### Expect
The wayland behaviour to match the xwayland behaviour
## Discussion
In firefox, this isn't a big issue because the notification anchor is to the left of the URL entry, so the notification will normally be able to extend to the right without any issue.
I'm not sure if there are places in firefox that spawn popup notifications on the right hand side.
However, in thunderbird, the notifications for addons or updates is anchored to the right of the top bar, so this cut off problem can appear even in full screen when using wayland. See Bug 1718653. In Thunderbird at least, my guess is that it is related to the `persistent` property for the popup notification (https://bugzilla.mozilla.org/show_bug.cgi?id=1718653#c4).
I thought maybe someone here might have a better idea about the problem.
|
|
1,709,832 | 15,397,053 |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36
Steps to reproduce:
I was writing a drag event handler on a `<table>`.
I needed to obtain the parent `<tr>` element while dragging over various nested elements, such as a `<div>` containing text inside `<td>`.
I was having trouble getting consistent results between browsers with `Node.nodeName`. So I decided to use `Element.closest()`.
Here's a quick HTML example of my markup nesting (it's not all that complicated):
```html
<tr>
<td>
Test 123<div>Test 123</div>
</td>
</tr>
```
Actual results:
It seemed to work, but I sometimes got this error: `Uncaught TypeError: event.target.closest is not a function`
Upon investigation, it only happens if `event.target` has a `nodeType` of `TEXT_NODE`. This appears to be a "Text Interface" according to MDN: https://developer.mozilla.org/en-US/docs/Web/API/Text.
It would seem that `Element.closest()` can only handle type `ELEMENT_NODE`.
Expected results:
The text node itself has a `parentElement` property that `Element.closest()` should be able to use. This bug does not occur in Chrome.
|
|
1,710,289 | 15,400,409 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
I clicked with middle mouse button on tab bar to open new tab.
Actual results:
New tab is opened and address bar is filled with paste buffer contents.
Expected results:
New tab should be opened and nothing should be pasted in tab bar
|
|
1,710,507 | 15,403,474 |
Created attachment 9221188
Context menu displayed as LTR
|
|
1,711,700 | 15,411,727 |
TypeError: can't access property "undefined", content.screens is undefined
AboutWelcomeDefaults.jsm:594:7
https://searchfox.org/mozilla-central/rev/0e8b28fb355afd2fcc69d34e8ed66bbabf59a59a/browser/components/newtab/aboutwelcome/lib/AboutWelcomeDefaults.jsm#594
I thought we fall back to the local default screens if there's no screen variable set in the experiment, e.g.,
https://experimenter.services.mozilla.com/nimbus/multistage-onboarding-remove-urlbar-focus
```
{
"id": "msw_control",
"template": "multistage"
}
```
But maybe something changed?
https://searchfox.org/mozilla-central/rev/0e8b28fb355afd2fcc69d34e8ed66bbabf59a59a/browser/components/newtab/aboutwelcome/AboutWelcomeChild.jsm#221,225,240,250
|
|
1,722,582 | 15,502,778 |
Created attachment 9233363
downloads.gif
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
Start a download on Firefox under Linux. I tested multiple distros like KDE, Ubuntu and Xfce and all had the same problem.
Actual results:
The background color of the download items in the library window has the same color as the progress bar of the actively downloaded file.
Expected results:
The background color of the download items should have a different color as the progress bar of the actively downloaded file. Also if I unselect an item in the downloads list and move the window then the first item gets selected again but that should not happen. During window movement the selection color changes and the dotted outline is removed which is weird and should not happen too.
|
|
1,717,451 | 15,459,119 |
Created attachment 9228134
Screencast from 21-06-21 16:53:01.webm
STR (seen in video):
1. Open the bookmark toolbar's context menu
2. Hover the mouse over the reload button in an attempt to show its tooltip (it won't show)
3. Wait a moment, then move the mouse off the button
4. Repeat 2 and 3, two more times
The UI hangs and many interactions become impossible.
Firefox Nightly (MOZ_ENABLE_WAYLAND)
GNOME 40.2, 3840x2400 scale 2
Arch Linux
Last good revision: 6df4f3b1c28850aee9fed46295f10beee79bb270
First bad revision: ac08d8af993569df8dedc278b251979897ab979d
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6df4f3b1c28850aee9fed46295f10beee79bb270&tochange=ac08d8af993569df8dedc278b251979897ab979d
|
|
1,764,319 | 15,855,752 |
Created attachment 9271909
firefox-popup.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0
Steps to reproduce:
* install an extension
* pin its icon to the overflow menu
* open the overflow menu and click on it
Actual results:
The popup is shown at the top left corner of firefox's window.
Expected results:
The popup should be shown near the overflow icon.
I've got a lot of crashes while doing mozregression. Here's what I can get:
13:18.01 INFO: Last good revision: 867b48058bde75ef267dc0620b39b3398a56989d
13:18.01 INFO: First bad revision: 8a83aa3ec30981da1a9affddb67339f55959e529
13:18.01 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=867b48058bde75ef267dc0620b39b3398a56989d&tochange=8a83aa3ec30981da1a9affddb67339f55959e529
|
|
1,767,321 | 15,881,718 |
After doing some poking around, it appears that there is a bug with the handling of content-disposition when doing a cross-process redirect handling, such as the one performed to display a downloaded document with `Content-Disposition: attachment` since bug 1756980.
This leads to issues where the document is incorrectly given the name "document.pdf" when saved from pdfjs after being redirected into a new tab to be served by the internal PDF viewer, as was noted by multiple commenters in bug 1756980.
|
|
1,762,816 | 15,842,175 |
From: https://www.reddit.com/r/firefox/comments/tvqzqn/firefox_99_takes_30s_to_startup/
>Firefox is too slow to startup on my Arch Linux box. It takes almost 30s to start on an SSD + Hexacore CPU.
ββ### Basic information
Steps to Reproduce:
Start Firefox.
Expected Results:
Actual Results:
30 second startup.
---
### Performance recording (profile)
Profile URL: https://share.firefox.dev/3DFu7VR
#### System configuration:
OS version: Arch Linux
GPU model: Intel(R) HD Graphics P630 (KBL GT2)
Number of cores: 8 (2 thread per core)
Amount of memory (RAM): 32G
### More information
>It was fine, until some days ago (I suspect it is an upgrade to 98/99 that made it this slow).
>Here what I've tried: - I uninstalled firefox, and reinstalled it. - Removed the .mozilla folder and retried. - Tried safe-mode, - Refreshed firefox and cleared cache ...
---
Thanks so much for your help.
|
|
1,706,259 | 15,370,172 |
This bug should address the following UX gaps per UX review:
- Make text size match other modal text size
- Increase space between elements (16px)
- Donβt focus element by default ('Choose a different application' and the 'Allow' checkbox on the 'Allow this site to open the ... link' modal get default focussed)
- Adjust checkbox text color to #5B5B66;
- Checkbox needs to be top align, not center align.
|
|
1,706,363 | 15,370,822 |
Created attachment 9217088
Screen Shot 2021-04-20 at 10.15.57 AM.png
The Search Tips that are shown when going to a search engine homepage are the color of the unfocused address bar. Screenshot attached.
The issue is that our [Urlbar background color rules](https://searchfox.org/mozilla-central/rev/b6f52976b562008c9d9ceeda22907e1eda506c8e/browser/themes/shared/urlbar-searchbar.inc.css#65,80,162,187) mostly depend on whether the Urlbar is `[focused="true"]` or not. Redirect Search Tips are a unique case where the Urlbar is open but not focused. Those CSS rules should consider both whether the Urlbar is focused and whether it's open.
|
|
1,706,384 | 15,370,910 |
Created attachment 9217104
screenshot
The banner in the protection panel for a reached milestone (x blocked tracker since y) does not fit the Proton style, like color and border-radius. Please see the bottom of the attached screenshot. The font size is also a bit too large. It was already larger than the other content before Proton but since Proton everything is bigger so this makes this element really big.
|
|
1,706,452 | 15,371,684 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
I updated to Firefox Nightly 90.0a1 (2021-4-20) in a Fedora 34 KDE Plasma installation. I started Firefox Nightly 90.0a1 (2021-4-20) on Wayland in Plasma 5.21.4 on Wayland with the following steps. Start konsole. Change to the directory Firefox Nightly 90.0a1 is in. MOZ_ENABLE_WAYLAND=1 ./firefox
Actual results:
Firefox Nightly 90.0a1 (2021-4-20) on Wayland started on X with the error glxtest: Could not connect to wayland socket shown in konsole and Troubleshooting Information > Graphics > Failure Log. The following errors were in Troubleshooting Information > Graphics > WebGL 1 Driver Renderer
WebGL creation failed:
* WebglAllowWindowsNativeGl:false restricts context creation on this system. ()
* Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS)
WebGL 2 Driver Renderer
WebGL creation failed:
* AllowWebgl2:false restricts context creation on this system. ()
Window Protocol xwayland
Desktop Environment kde
The compositor was OpenGL instead of the default WebRender. The WebGL Driver Renderer errors also happened when I started 90.0a1 (2021-4-20) on X with MOZ_ENABLE_WAYLAND=0 ./firefox
These errors didn't happen with 90.0a1 (2021-4-19) or earlier. I ran MOZ_ENABLE_WAYLAND=1 mozregression --bad 2021-4-20 --good 2021-4-19
5:55.96 INFO: Narrowed integration regression window from [cb69b22f, f8eb1926] (3 builds) to [30af8f80, f8eb1926] (2 builds) (~1 steps left)
5:55.96 INFO: No more integration revisions, bisection finished.
5:55.96 INFO: Last good revision: 30af8f80e2754783f1981485dd911a2e341d9afd
5:55.96 INFO: First bad revision: f8eb1926bfdbb630b4aa17e064c3472c4a32709e
5:55.96 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=30af8f80e2754783f1981485dd911a2e341d9afd&tochange=f8eb1926bfdbb630b4aa17e064c3472c4a32709e
The first bad revision f8eb1926bfdbb630b4aa17e064c3472c4a32709e had the following changes.
User
Push date [To Local] Changeset Patch author β Commit message
[email protected]
Tue Apr 20 01:59:31 2021 +0000 f8eb1926bfdbb630b4aa17e064c3472c4a32709e Mike Hommey β Bug 1377445 - Remove gtk+2 from docker images. r=firefox-build-system-reviewers,andi,mhentges
0ce69d9f596b3910876f4838c5b04250a553b9c4 Mike Hommey β Bug 1377445 - Remove build dependencies on gtk+2. r=firefox-build-system-reviewers,mhentges
44d676a26d1a8c6514eca25ef4310e7f2a9df873 Mike Hommey β Bug 1377445 - Use dlsym for atk_bridge_adaptor_init. r=eeejay
Expected results:
Firefox Nightly 90.0a1 on Wayland would start normally without errors.
|
|
1,706,459 | 15,371,720 |
When the string is not found, the input box will have a red highlight: https://searchfox.org/mozilla-central/rev/9b430bb1a11d7152cab2af4574f451ffb906b052/toolkit/themes/shared/findBar.inc.css#77-79
This `#E22850` color looks very similar to the Linux system color, so it can be confusing for users and make it difficult to differentiate between highlights.
:ntim suggested we adjust the `moz-accent-color` in the find bar to `color-mix(in srgb, -moz-accent-color 50%, transparent)` to create a better distinction
|
|
1,706,777 | 15,373,816 |
According to the specification, if the user is hovering the "Find in folder" button, then it should use the "ghost button" hover/active states. If they're hovering any other part of the download item, then the entire download item should show the current hover state.
I'm not 100% sure this can be done with CSS - the cascade doesn't let us affect the state of the containing download item element when hovering the child find-in-folder item.
|
|
1,707,177 | 15,376,348 |
Created attachment 9217949
screenshot: update available app menu badge
Firefox 90.0a1 20210422093115 on Windows 8.1 with 125% zoom on OS level
The app menu badge for an available update is so tiny and blurry that the arrow is unrecognizable.
Steps to reproduce:
1. Install not the latest build.
2. Disable automatic updates in the Settings (it might be necessary to start it with the `-offline` argument from the command line to be able to change this before it gets updated to the latest version).
3. Go online (Alt key > menu File).
4. Wait for update to get detected or trigger the background check (haven't the code at hand).
|
|
1,694,820 | 15,281,553 |
Created attachment 9205238
not-aligned.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.190 Safari/537.36
Steps to reproduce:
Open the Calendar tab and view the difference between a time-ranged event versus an all-day event. Please see my attached screenshot.
I'm using Thunderbird 78.8.0 (32-bit), on Windows 10 20H2.
Actual results:
For time-ranged events, the time and event name are not vertically aligned with each other. There's about a 2-pixel shift in positioning.
Expected results:
The time and event name should be vertically aligned.
|
|
1,696,319 | 15,293,406 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
As of the 2021-03-03-09-41-10-mozilla-central night build, Firefox fails to start with
/tmp $ ./firefox/firefox -no-remote -profile /tmp/ff/
./firefox/firefox: symbol lookup error: /tmp/firefox/libxul.so: undefined symbol: gdk_wayland_display_get_type
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b2c9624b48f0dc756adcba7cd43a941f349720f6&tochange=478d2e18554dfcdde9876073614a2c4973cb6e1c
Possibly Bug 1622107 introducing a call to gfxPlatformGtk::GetPlatform()->IsWaylandDisplay()
This is running on Gentoo Linux with gtk+-3.24.24 build with wayland support disabled.
|
|
1,703,625 | 15,349,599 |
Created attachment 9214170
Profiler_menu_screenshot.jpg
### Steps to reproduce
1. Set `browser.proton.contextmenus.enabled` pref = true.
2. In about:addons, change the Firefox theme to "Dark" ("A theme with a dark color scheme.").
3. Load https://profiler.firefox.com/
4. Click the "Enable Profiler Menu Button" button.
5. Click the profiler toolbar button's down arrow to expand the profiler menu.
6. Expand the profiler menu's "Settings" drop-down list.
### Expected result
The list of profiler settings should be readable.
### Actual result
The list is unreadable because the setting names are dark text on a dark background color. See the attached screenshot.
I bisected this regression to this pushlog for bug 1682522:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=bf6cf886b9683288fa453a66f999875b6ff6d3eb&tochange=a1f8152b4981d05ae1f5edaa5cb2035e20d38564
|
|
1,703,930 | 15,351,653 |
Steps to reproduce:
1. In a fresh profile, open the Bookmarks menubar menu.
2. Go to the "Firefox Nightly Resources" folder.
3. Move your mouse over the bookmarks in that folder, and watch the target URL being displayed in the bottom left corner of the browser window.
4. Move your mouse outside of the submenu.
5. Click outside the menu to dismiss it.
Expected results:
When the mouse leaves the bookmark menu items, the URL should disappear.
Actual results:
The URL of the last-hovered item remains, even after the menu has been dismissed.
This is because the native menu code only fires `DOMMenuItemActive` events but no `DOMMenuItemInactive` events.
|
|
1,704,404 | 15,354,562 |
Created attachment 9214999
Screenshot of the bug
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
Opened a web page composed of the following HTML code (the title was originally found in a YouTube video):
<html>
<head>
<title>π§ππ ππ‘πππππ‘π§ - YouTube</title>
</head>
</html>
Note: I tested it on a clean profile, and it still happens.
Actual results:
The tab bar became much taller than required to show the title. (see attached screenshot)
Expected results:
The tab bar staying the same size, as no additional height is required to display the title.
|
|
1,704,817 | 15,358,941 |
Created attachment 9215462
Screen Shot 2021-04-13 at 10.12.33 AM.png
## steps to reproduce/what did you do?
* First, tab through the chrome to observe the dark/neon blue focus ring color (depending on the theme you have chosen)
* Now tab into one of the dropdown menus like Application menu or Library
## expected behavior/ what did you think will happen?
* Focus ring color is blue like the rest of the chrome
## actual behavior/ what actually happened
* Focus ring color uses my system accent color (in my case, orange)
## additional notes
For me, the issue is not so much that it's one color or the other, it's that it's inconsistent. Especially in dark theme where the orange sticks out.
|
|
1,705,120 | 15,361,220 |
STR:
1. Set `widget.macos.native-context-menus` to true.
2. Open a folder in the bookmarks toolbar. Right click on one of the bookmarks.
3. Click Open in New Tab.
Expected: The native menu closes, the bookmarks toolbar folder menu closes, and the link opens in a new tab.
Actual: The native menu closes and the link opens in a new tab. The bookmarks toolbar folder menu remains open.
This is causing `browser/components/enterprisepolicies/tests/browser/managedbookmarks/browser_policy_managedbookmarks.js` to fail. Once the synthesized clicks on the context menu in that test are replaced with `activateItem`, the test still fails. The first part of the test selects Open in New Tab in the native context menu. The next part wants to test something else, so it reopens the bookmarks folder menu and waits for the folder menu's popupshowing event. Since the event never fires (since the folder menu is still open), the test hangs.
|
|
1,705,447 | 15,363,220 |
## steps to reproduce/what did you do?
- Attempt to install an Extension or Theme, the menu to confirm the installation displays an Add button
- Open the Bookmark browser action , the menu to save the bookmark displays a Save button
## expected behavior/ what did you think will happen?
- Confirmation button uses browser theme color
## actual behavior/ what actually happened?
- Confirmation button uses system accent color
|
|
1,705,562 | 15,364,208 |
Due to recent changes to the toolbar padding now the urlbar and searchbar box-shadow is cut, that's quite visible in Light.
I was trying a `box-shadow: 0 1px 3px rgba(0, 0, 0, 0.23);` as an alternative, there's no spec for this toolbar size, we may have to test and get an ok from UX.
|
|
1,701,019 | 15,329,304 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
Firefox 87.0 on CentOS 7.9 - File --> Print (the new style print modal comes up)
Actual results:
The only destination available is Save to PDF. I have to select 'Print using the system dialog' to see my printers.
Expected results:
All of my printers should be in the destinations drop down. Note: I have 136 printers defined (via CUPS client).
I have tested Firefox nightly 89.0a1 and the problem still exists there.
I have also tested this on openSUSE Leap 15.2 and the problem does not exist there (I have 133 printers on that system).
|
|
1,701,041 | 15,329,405 |
1. The gap between the top of the panel and the panel description should be 16px. Currently, it appears to be closer to 20px.
2. The gap between the bottom buttons and the bottom of the panel should also be 16px. Currently, it appears to be closer to 19px.
3. The menulists in the WebRTC panels have too much of a gap between the end of the menulist and the right side of the panel. The gap should be 16px in total.
4. The large-style menulists are too tall. The ones in the WebRTC panel are 36px in height, when they should be 32px.
5. The gap between an un-iconed menulist label and its starting edge should be 16px. Currently, it appears to be 20px.
6. Similarly, there should be 16px spacing around the dropdown icon on its right side, and 8px of spacing above and below the icon.
|
|
1,701,055 | 15,329,452 |
There should be a 4px margin above the Learn more link, and 16px below.
|
|
1,701,637 | 15,334,678 |
Created attachment 9212169
Screen Shot 2021-03-29 at 8.09.28 AM.png
The submenus in the bookmarks toolbar button are styled like native menus, at least on macOS. We appear to apply the Secondary Hover bgcolor to them on hover. This is very low-contrast. We might consider using a blue/system Highlight hover bgcolor for the items in these submenus.
|
|
1,702,298 | 15,339,316 |
Created attachment 9212876
Bookmarks Panel
On smaller screen sizes, the bottom of the bookmarks panel isn't accessible when fully expanded.
|
|
1,702,309 | 15,339,357 |
Reproducible: Only if Proton is enabled.
Steps to reproduce:
1. Too many bookmarks in folder(incl. chevron) so that bookmarks menupopup will be overflowed.
2. Open bookmarks folder/chevron
3. Drag a bookmark to the edge of the screen(Fitts's law) to scroll the menupopup
Actual Results:
The menupopup unexpectedly closes
Expected Results:
The menupopup should not close.
|
|
1,702,999 | 15,345,107 |
STR:
1. Click on the Bookmarks button in the URL bar
2. Click on the expander next to the folder selector menulist
3. Click on the button to create a new folder (bottom of the tree selector)
ER:
The new entry in the tree should show a folder icon to the left of the text input.
AR:
The new entry in the tree only shows the text input, and the folder doesn't appear until the user completes filling in the text input.
|
|
1,692,497 | 15,262,312 |
Created attachment 9202888
TB_78.7.2_OpenPGP_Aliases_MessageSecurityInfo-20210211_22-35-32.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
I sent an encrypted message to 10+ recipients with available and valid keys. Afterwards I want to check encryption information of that mail by clicking on the "OpenPGP" button at the right side of the message header (in folder "Sent").
Actual results:
TB (78.7.2 Daily) on Debian 10 (Gnome) only shows the first six recipients, but indicates that there are more recipients. Unfortunately I cannot scroll down the list, as there is no scroll bar on the right side of the popup window, nor can I use the mouse wheel.
Expected results:
Popup window is supposed to show all recipients here, with a scroll bar, if there are more recipients than can be shown at once.
|
|
1,693,460 | 15,270,988 |
Created attachment 9203886
Screenshot from 2021-02-18 06.34.05.png
In the latest nightly (20210217213226) the CSD rendering is completely broken for me on elementary OS. Not only does the window get a normal title bar, but it also has an invisible area around it that it doesn't draw to (even though the WM is convinced the space is used by the window). Interestingly, the native titlebar is still within this transparent area. See the attached screenshot.
According to moz regression this is due to patches from bug 1681356:
2:28.87 INFO: Last good revision: 3d4360e021fa62a3dfc40df2295038622f7cfa96
2:28.87 INFO: First bad revision: d6388772d4c63331ad4dfebdbaa945364dada2e1
2:28.87 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3d4360e021fa62a3dfc40df2295038622f7cfa96&tochange=d6388772d4c63331ad4dfebdbaa945364dada2e1
|
|
1,693,472 | 15,271,052 |
Description:
I'm using Firefox Nightly 87.0a1 on Wayland with WebRender enabled in a Fedora 34 KDE Plasma installation. When I click on menus in the menu bar of Firefox Nightly 86.0a1 (2021-1-15) - 87.0a1 (2021-2-17), the menu items under the cursor usually aren't highlighted. Sometimes just the first item in the menu was highlighted. Occasionally multiple items in the menu were highlighted at the same time. The menus shown when right-clicking on a page are also affected by this issue. This problem started with 86.0a1 (2021-1-15). I ran the following to look for the commit involved
MOZ_ENABLE_WAYLAND=1 mozregression --good 2021-1-13 --bad 2021-1-18
The end of the process showed
13:17.81 INFO: Narrowed integration regression window from [25680895, 8a9e98e5] (4 builds) to [376c2ff6, 8a9e98e5] (2 builds) (~1 steps left)
13:17.81 INFO: No more integration revisions, bisection finished.
13:17.81 INFO: Last good revision: 376c2ff62872fbf7cc25803f9cbdcd42f8c1fe6c
13:17.81 INFO: First bad revision: 8a9e98e50d031c7a72429a08aad7325f50e34d2e
13:17.81 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=376c2ff62872fbf7cc25803f9cbdcd42f8c1fe6c&tochange=8a9e98e50d031c7a72429a08aad7325f50e34d2e
The first bad revision was https://hg.mozilla.org/integration/autoland/rev/8a9e98e50d031c7a72429a08aad7325f50e34d2e
Bug 1686703 [Wayland] Merge GetWaylandBufferWithSwitch()/GetWaylandBufferRecent() to GetWaylandBuffer(), r=jhorak
Depends on D101746
Differential Revision: https://phabricator.services.mozilla.com/D101747
The problem doesn't affect 86.0a1-87.0a1 on X in Plasma on Wayland with the same Firefox settings and system versions.
Steps to reproduce:
1. Boot a Fedora 34 KDE Plasma installation updated to 2021-2-17
2. Log in to Plasma 5.21.0 on Wayland
3. Install or update to Firefox Nightly 87.0a1 (2021-2-17)
4. Start Nightly on Wayland with WebRender enabled
MOZ_ENABLE_WAYLAND=1 ./firefox
5. Select the Bookmarks menu
6. Move the cursor down over the Bookmarks menu
7. Repeat 5-6 for other menus in the menu bar
8. Go to a site such as https://bugzilla.mozilla.org
9. Right-click somewhere on the page
10. Move the cursor up and down the right-click menu
Versions:
Firefox Nightly 86.0a1 (2021-1-15) - 87.0a1 (2021-2-17)
gtk3-3.24.25-2.fc34.x86_64
plasma-desktop-5.21.0-2.fc34.x86_64
qt5-qtbase-5.15.2-13.fc34.x86_64
kf5-plasma-5.79.0-2.fc34.x86_64
mesa-dri-drivers-21.0.0~rc4-1.fc34.x86_64
|
|
199,134 | 1,793,433 |
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4a) Gecko/20030311
Build Identifier: mozilla-source.tar.gz 24-Mar-2003 14:31
I build FreeBSD nightly build every day.
But building mozilla is failed on FreeBSD 4.7-RELEASE
since few days ago.
% env MOZILLA_OFFICIAL=1 BUILD_OFFICIAL=1 \
GLIB_CONFIG=/usr/local/bin/glib12-config \
GTK_CONFIG=/usr/X11R6/bin/gtk12-config \
LIBIDL_CONFIG=/usr/local/bin/libIDL-config-2 \
gmake -f client.mk build
(snip)
gmake[4]: Entering directory `/ide3/mozilla/mozilla/security/nss/cmd/shlibsign'
cd mangle; gmake -j1 export
gmake[5]: Entering directory
`/ide3/mozilla/mozilla/security/nss/cmd/shlibsign/mangle'
gmake[5]: Nothing to be done for `export'.
gmake[5]: Leaving directory
`/ide3/mozilla/mozilla/security/nss/cmd/shlibsign/mangle'
Tue Mar 25 22:29:29 JST 2003
gcc -o FreeBSD4.7_OPT.OBJ/shlibsign -O -fPIC -ansi -Wall -DFREEBSD
-DHAVE_STRERROR \
-DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so\" -DSHLIB_PREFIX=\"lib\"
-UDEBUG -DNDEBUG \
-D_THREAD_SAFE -D_REENTRANT -I/usr/X11R6/include
-I/ide3/mozilla/mozilla/dist/include \
-I../../../../dist/public/nss -I../../../../dist/private/nss
-I../../../../dist/include \
-I/ide3/mozilla/mozilla/dist/include/nspr
-I/ide3/mozilla/mozilla/dist/include/dbm \
-I../../../../dist/public/dbm -I../../../../dist/public/seccmd
FreeBSD4.7_OPT.OBJ/shlibsign.o \
/ide3/mozilla/mozilla/dist/lib/libsectool.a
-L/ide3/mozilla/mozilla/dist/lib/ -lssl3 -lsmime3 \
-lnss3 -lplc4 -lplds4 -lnspr4
/usr/libexec/elf/ld: warning: libsoftokn3.so, needed by
/ide3/mozilla/mozilla/dist/lib//libnss3.so, not found (try using -rpath or
-rpath-link)
/ide3/mozilla/mozilla/dist/lib//libnspr4.so: undefined reference to
`pthread_cond_signal'
(snip)
/ide3/mozilla/mozilla/dist/lib//libnss3.so: undefined reference to
`NSC_GetFunctionList'
(snip)
gmake[4]: *** [FreeBSD4.7_OPT.OBJ/shlibsign] Error 1
gmake[4]: Leaving directory `/ide3/mozilla/mozilla/security/nss/cmd/shlibsign'
It seems lack of '-pthread -lsoftokn3'.
After failing build, run gmake with "LDFLAGS+='-pthread -lsoftokn3'" is succeed.
% cd /ide3/mozilla/mozilla/security/nss
% gmake -C ../../security/nss/cmd/shlibsign MAKE="gmake -j1" -j1 \
MOZILLA_INCLUDES="-I/ide3/mozilla/mozilla/dist/include/nspr
-I/ide3/mozilla/mozilla/dist/include/dbm" \
SOURCE_MD_DIR=/ide3/mozilla/mozilla/dist DIST=/ide3/mozilla/mozilla/dist
MOZILLA_CLIENT=1 NO_MDUPDATE=1 \
BUILD_OPT=1 NS_USE_GCC=1 NS_USE_NATIVE= LDFLAGS+='-pthread -lsoftokn3'
But, I can't make suitable patch.
Reproducible: Always
Steps to Reproduce:
% fetch http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-source.tar.bz2
% tar yxf mozilla-source.tar.bz2
% cd mozilla
% cat > .mozconfig <<EOF
ac_add_options --enable-optimize="-O"
ac_add_options --disable-debug
ac_add_options --enable-strip
ac_add_options --disable-tests
ac_add_options --enable-crypto
ac_add_options --enable-extensions=default,irc
ac_add_options --with-pthreads
EOF
% env MOZILLA_OFFICIAL=1 BUILD_OFFICIAL=1 \
GLIB_CONFIG=/usr/local/bin/glib12-config \
GTK_CONFIG=/usr/X11R6/bin/gtk12-config \
LIBIDL_CONFIG=/usr/local/bin/libIDL-config-2 \
gmake -f client.mk build
|
|
167,375 | 1,533,090 |
User-Agent: Mozilla/5.0 (X11; U; BSD/OS i386; en-US; rv:1.1) Gecko/20020827
Build Identifier: Mozilla/5.0 (X11; U; BSD/OS i386; en-US; rv:1.1) Gecko/20020827
Out of the box (ok, the tip of the CVS tree as of a couple of days ago)
the build/configuration system doesn't recoginize BSD/OS 5.0. Since 5.0
has more or less the same userland code as BSD/OS 4.3, it wasn't too
hard to wedge in recoginition for the system into Mozilla.
Reproducible: Always
Steps to Reproduce:
1. Checkout the source tree onto a BSD/OS 5.0 machine
2. Attempt a build.
3. Notice it fails.
Actual Results:
It doesn't build.
Expected Results:
It should build.
Since there isn't a place to attach a diff in this particular bugzilla
form, I'll attach the diffs needed to make it build in just a minute.
|
|
130,359 | 1,216,973 |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.9) Gecko/20020310
BuildID: 2002031005
Reproducible: Sometimes
Steps to Reproduce:
1. Launch Mail & News, connect to IMAP server
2. Select message in thread pane
Actual Results: Since upgrading to 0.9.9 (today):
(1) Some messages display OK.
(2) Some display only the first few lines (and nothing in "View Source")
(3) Some cause hang (spinning beachball, 80% CPU, have to force quit)
(4) Some cause complete crash (see backtrace attached)
Expected Results: All messages should download and display.
(0.9.8 and subsequent nightlies gave me none of those problems, except maybe (2)
sometimes.)
If that matters:
β’ The IMAP account is over SSL
β’ I'm using 3-pane view
β’ Backtrace below was when downloading a mulitipart message
(sourceforge mailing list digest), but I also got crashes
on simpler messages.
|
|
699,447 | 5,823,866 |
Steps to Reproduce:
1. Register a non-vouched account on mozillians.org
2. Confirm the account
3. Log-in and go to "profile"
4. Click on "edit profile"
5. Try to add a few groups
6. Submit the changes
Actual Results:
I can't add groups to my profile.
Expected Results:
I should be able to add groups to my profile and make it easier to find me!
|
|
308,838 | 2,613,105 |
Using today's Win32 installer builds, SeaMonkey fails to start after installation.
I suspect bug 299992.
My self-built SeaMonkey trunk Win32 opt builds and starts just fine, so this is
limited to the installer, which makes me think of this GRE change.
Steps to Reproduce:
1. Grab a seamonkey-1.1a.en-US.win32.installer.exe or
seamonkey-1.1a.en-US.win32.stub-installer.exe build from
ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/
2. Install, and wait for the app to launch.
Expected Results:
SeaMonkey should auto-launch itself after a successful installation.
Actual Results:
Nothing happens. Manually double-clicking the .exe doesn't work either.
|
|
24,251 | 167,094 |
build: Apprunner
version: 2000011408
Platform: Mac
Other Platforms: Have yet to check on Linux or Windows
Expected Results: Apprunner should display the empty iframe (since the format is
not supported) and not freeze.
What I got: Opening the attached file results in a freeze.
Steps to reproduce:
1) Open the attached file in apprunner.(source reference is .pdf)
2) The window is balck and application freezes.
|
|
78,725 | 702,645 |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.19 i686; en-US; rv:0.9+) Gecko/20010503
BuildID: 2001050306
Right-clicking on an empty area of the document doesn't always
bring up the context menu.
I'm not sure what makes it work sometimes. It appears to work
for links/images, and then once on an empty part of the document,
but not again.
Reproducible: Sometimes
Steps to Reproduce:
1. Open any page (like about:blank)
2. Right-click to bring up the context menu.
3. Right-click again somewhere else.
Actual Results: No menu!
Expected Results: Expected to see the context menu again.
My last nightly was 20010430??, and it worked fine there, so it
was something recent.
|
|
112,978 | 1,050,908 |
steps to reproduce.
open the following html in mozilla.
------------------------
<html>
<title> Select List </title>
<body>
<!-- Test Select List -->
<u><b>Testing Select List</b></u>
<br><br>
Choose your favorite color
<select>
<option> Red </option>
<option> Blue </option>
<option> Green </option>
<option> Yellow </option>
</select>
</body>
</html>
--------------------------------
open mozInspect and click on "Show Hightlight rectangle" button. Then click on
select list values. we donot get the focus on the values.the focus is only on
the drop down list window. In IE we see the focus on each list item.
|
|
105,906 | 983,670 |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5+)
Gecko/20011019
BuildID: 2001101909
When autocomplete for the MailNews To: field gets activated, it completely hangs
Mozilla.
Reproducible: Always
Steps to Reproduce:
1. In MailNews, compose a new message (e.g. with CTRL+M).
2. Start typing in the To: field.
3. After a few chars, stop typing so that autocomplete jumps in.
Actual Results: Hang with 100% CPU. Mozilla does not respond any more at all.
Expected Results: An autocomplete result (if available).
This bug happens even after the first char if I pause after typing it.
It doesn't matter whether the typed string would actually lead to a result.
(E.g. typing ajasdfhjasdf triggers this bug as well.)
URL bar autocomplete seems to work fine, though.
|
|
9,398 | 70,880 |
Linux (1999-07-07-08 m8)
Summary: When selecting an imap server from the folder pane, apprunner crashes.
This only happens on multiple servers (1 pop, 1imap and 1 news server) only
Steps to reproduce:
1. Use a prefs50.js file that only consists of 1 pop, 1 imap and 1 news server
2. Open Messenger from the Tasks menu
3. Click on the pop server from the folder pane, it works fine.
4. Click on the news server, it displays the news group folders, no problem
5. But when I click on the Imap server, crash immediately occurs.
Note: I try using one imap account, it works fine. And I try a prefs50.js file
that consists of 5 multiple IDs ( 2pop, 2 imap, and 1 news server), no crash
either. This only happens to the 3 multiple ids only
This does not occur on Win_nt and Mac.
Reproducible consistently.
Here is the stack trace:
in nsTableRowGroupFrame::CalculateRowHeights ()
#1 0x409ca6eb in nsTableRowGroupFrame::Reflow ()
#2 0x408c0667 in nsContainerFrame::ReflowChild ()
#3 0x409c1bfc in nsTableFrame::ReflowMappedChildren ()
#4 0x409c0364 in nsTableFrame::ResizeReflowPass2 ()
#5 0x409bfd84 in nsTableFrame::Reflow ()
#6 0x409dc663 in nsTreeFrame::Reflow ()
#7 0x408c0667 in nsContainerFrame::ReflowChild ()
#8 0x409c5156 in nsTableOuterFrame::IR_InnerTableReflow ()
#9 0x409c4b9e in nsTableOuterFrame::IR_TargetIsInnerTableFrame ()
#10 0x409c4b60 in nsTableOuterFrame::IR_TargetIsChild ()
#11 0x409c4ac6 in nsTableOuterFrame::IncrementalReflow ()
#12 0x409c5cf8 in nsTableOuterFrame::Reflow ()
#13 0x408be5b1 in nsBlockReflowContext::ReflowBlock ()
#14 0x408ba84d in nsBlockFrame::ReflowBlockFrame ()
#15 0x408b9e38 in nsBlockFrame::ReflowLine ()
#16 0x408b9b7e in nsBlockFrame::ReflowDirtyLines ()
#17 0x408b93c7 in nsBlockFrame::Reflow ()
#18 0x409d5ad4 in nsBoxFrame::FlowChildAt ()
#19 0x409d5a26 in nsBoxFrame::FlowChildAt ()
#20 0x409d5396 in nsBoxFrame::FlowChildren ()
#21 0x409d506e in nsBoxFrame::Reflow ()
#22 0x408c0667 in nsContainerFrame::ReflowChild ()
#23 0x408c8322 in RootFrame::Reflow ()
#24 0x408c0667 in nsContainerFrame::ReflowChild ()
#25 0x408e6090 in ViewportFrame::Reflow ()
#26 0x408c91ec in nsHTMLReflowCommand::Dispatch ()
#27 0x408dac4a in PresShell::ProcessReflowCommands ()
#28 0x408d98c6 in PresShell::ExitReflowLock ()
#29 0x408db790 in PresShell::ContentInserted ()
#30 0x4069cafc in XULDocumentImpl::ContentInserted ()
#31 0x40683a3b in RDFElementImpl::InsertChildAt ()
#32 0x4068b5e3 in RDFGenericBuilderImpl::OnSetAttribute ()
#33 0x4069f523 in XULDocumentImpl::OnSetAttribute ()
#34 0x4068296a in RDFElementImpl::SetAttribute ()
#35 0x40294bb1 in NS_NewScriptDocumentType ()
#36 0x4030a272 in js_Invoke ()
#37 0x4030ff0e in js_Interpret ()
#38 0x4030a2c0 in js_Invoke ()
#39 0x4030ff0e in js_Interpret ()
#40 0x4030a2c0 in js_Invoke ()
#41 0x4030ff0e in js_Interpret ()
#42 0x4030a2c0 in js_Invoke ()
#43 0x4030a495 in js_InternalCall ()
#44 0x402f531d in JS_CallFunctionValue ()
#45 0x40299960 in nsJSEventListener::HandleEvent ()
#46 0x408b2a19 in nsEventListenerManager::HandleEvent ()
#47 0x406854ff in RDFElementImpl::HandleDOMEvent ()
#48 0x4068555c in RDFElementImpl::HandleDOMEvent ()
#49 0x4068555c in RDFElementImpl::HandleDOMEvent ()
#50 0x4068555c in RDFElementImpl::HandleDOMEvent ()
#51 0x4068555c in RDFElementImpl::HandleDOMEvent ()
#52 0x4068555c in RDFElementImpl::HandleDOMEvent ()
#53 0x4068555c in RDFElementImpl::HandleDOMEvent ()
#54 0x408b46ec in nsEventStateManager::CheckForAndDispatchClick ()
#55 0x408b3acc in nsEventStateManager::PostHandleEvent ()
#56 0x408dbfa6 in PresShell::HandleEvent ()
#57 0x40acc7bd in nsView::HandleEvent ()
#58 0x40ad3fad in nsViewManager::DispatchEvent ()
#59 0x40acb26e in _init ()
#60 0x401a1f26 in nsWidget::DispatchEvent ()
#61 0x401a1e7d in nsWidget::DispatchWindowEvent ()
#62 0x401a1fa3 in nsWidget::DispatchMouseEvent ()
#63 0x401a272b in nsWidget::OnButtonReleaseSignal ()
#64 0x401a2a6b in nsWidget::ButtonReleaseSignal ()
#65 0x80c4748 in gtk_window_set_default_size ()
#66 0x809d5a3 in gtk_signal_connect_object ()
#67 0x809cc2a in gtk_signal_connect_object ()
#68 0x809b366 in gtk_selection_data_set ()
#69 0x80bce90 in gtk_widget_size_request ()
#70 0x80864e5 in gtk_get_current_event ()
#71 0x8085a86 in gtk_main_iteration_do ()
#72 0x80d415b in gdk_input_add ()
#73 0x80e70e0 in g_list_length ()
#74 0x80e755b in g_list_length ()
#75 0x80e7675 in g_main_iteration ()
#76 0x808559b in gtk_main ()
#77 0x401977a3 in nsAppShell::Run ()
#78 0x400fe16a in nsAppShellService::Run ()
#79 0x8052406 in main ()
|
|
6,896 | 51,492 |
Steps to reproduce :
(1) launch build
(2) open editor
(3) click in window and start typing periods. it will act as a forward delete
What the problem is :-
nsEventListener.cpp is processing key downs incorrectly. The problem is that,
nsKeyDown is handling both virtual key and character events on the same handler.
It is comparring the virtual keycode for VK_DELETE with the character code for
'.', which happen to be the same.
if (PR_FALSE==keyProcessed)
{
switch(keyCode) {
case nsIDOMUIEvent::VK_BACK:
mEditor->DeleteSelection(nsIEditor::eDeleteLeft);
break;
case nsIDOMUIEvent::VK_DELETE:
mEditor->DeleteSelection(nsIEditor::eDeleteRight);
break;
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.