Diễn đàn hỗ trợ Firefox

Good evening. Since a few days (since installed ver 124) I'm unable to use the "repeatability" from keyboard. I couldn't find any adjustment option in configuration to manage this. I tried outside (with other programs) and it works fine. Maybe its me, that I'm missing some adjustment. Would you guide me about this, please? Thanks in advance!

Orlando Sposto

PD: OS: Linux ver 22.04 Browser: obviously Firefox version 124.0.1 64bits machine achitecture: Pentium i7 Main problem: when in X, repetition is null or very slow. Regards.

Despite having logged into Which? via FireFox, and accepted all cookies I am asked again and again on every Which? page about cookies.

How can I stop this?

Is this Which? or FF?

I just updated Firefox. That's supposed to improve things, right?

Now the address bar is gray most of the time. It looks normal when I'm entering a search, or editing a URL, the rest of the time, it's just ugly now. I don't like things to be changed arbitrarily like that. What is the rationale for changing the way that looks? How can I change it back? Please give me a setting, or about:config preference, and please don't get direct file editing involved, okay?

Why doesn't tiling the windows work as well as it used to? Yesterday, I could hit super+left, or super+right, from a maximized window, and it'd tile to the left or right side of the screen perfectly, the first time, every time, no problems. Now it has an intermediate stage where there's a gap all the way around the window. It seems to improve by clicking on a different window, then back into the Firefox window, but that intermediate step just shouldn't happen! What's a fix for this?

I also hit the button at the bottom to include optional troubleshooting information, but it said instead, "We can't automatically get your browser's troubleshooting data, please try these manual steps." No, I'm not doing that, get that thing working right, too!

when trying to acsess the gop3.nl site, i get the folowing error dump An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was: RuntimeError: indirect call to null @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[117365]:0x1f90a96 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[49943]:0xf1418d @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[1707]:0x113fc2 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[127477]:0x2191221 invoke_iiiii@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:474355 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[49984]:0xf17b02 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[105819]:0x1d74f24 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[127471]:0x2191119 invoke_viiiiii@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:477540 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[49985]:0xf17e47 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[10167]:0x2c1f3b @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[127465]:0x21910a7 invoke_viiiiiii@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:476885 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[104662]:0x1d1a184 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[10167]:0x2c1f3b @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[28099]:0x819f13 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[28075]:0x8177fd @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[19380]:0x5759a0 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[117706]:0x1f9c26e @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[1165]:0x100567 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[56630]:0x10a5c7c @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[117697]:0x1f9ba9a @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[684]:0xefff4 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[175959]:0x2cd6bc3 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[7550]:0x22fb3d @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[22366]:0x6d2066 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[127479]:0x2191239 invoke_iiii@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:474006 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[3472]:0x15e211 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[44412]:0xd8b149 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[21250]:0x62b91d @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[1279]:0x103bd4 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[31789]:0x90f83b @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[31789]:0x90f8ec @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[60397]:0x1201b9f @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[133311]:0x2356fc6 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[60817]:0x1230490 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[60823]:0x123134c @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[60823]:0x12313bd @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[60193]:0x11d36d1 @https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.wasm.gz:wasm-function[127472]:0x2191121 browserIterationFunc@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:254637 callUserCallback@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:207835 runIter@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:209111 Browser_mainLoop_runner@https://cdn-files-live.gop3.nl/clients/85d12980b5de4b0341b4f9ccaa6079752a7b1531/Build/WebGL.framework.js.gz:3:207370

FF112 encountered this exact eror beginning march 7. upgrading to F123 default setings has not helped. Is this eror indicating only a certain browser can continue to the website?

thanks aand regards

Hi

When I scroll text for some reason, Firefox stopping scrolling very slow. It's almost take up to 2 seconds. Very annoying smoothest. I have stopped scrolling already but Firefox still scrolling and finally very slow stop it. I can't focus on the text because it's still slows down the scrolling.

How to fix that!?

Every time I turn on my computer or try to access G Mail and Google Calendar, I have to sign in. This did not happen in previous versions (I am now using 124.0).

Can anyone explain why this is so? I am missing something?

Will appreciate any guidance to solve this issue.

Hector

I have some new issues after a recent update.

The tab bar fades when the window isn't focused. I certainly didn't have it set to do that before, and I have had no luck finding the setting for it. Tell me what the setting is?

Another I'd like to know the setting for, is the behavior of the address bar. It used to always be white, and now it's gray unless I'd entering something in it. I'd like to switch the setting back to the other way.

I've tried hunting for the settings for these things, but it has not been intuitive for me, and I guess I keep overlooking the pertinent settings somehow. Please tell me what parts of the settings page, or what about:config entries, will get things put back as I had them?

As third parties cookies will going to be blocked and Google is migrating their identity services to fedcm but currently fedcm is not supported by Mozilla so what will be the solution for one tap sign in using google on Mozilla?

So is that true that Firefox is consume more RAM than Chrome in this Ai era(2024)? & 2nd question is my deepin os Firefox is sometime crash and closed automatically! why & how to fix this non-sense ?

I'm not sure when it happened, but somewhere along the line, Firefox stopped showing on-hover tooltips on unfocused windows. Clicking into the Firefox window again can disrupt what I'm doing in another window, however. For example trying to hover on the Firefox window with my mouse cursor, and type the text of the tooltip into a different window, while leaving the tooltip visible. Wrecks that idea!

I guess I assumed it'd be a temporary issue, that'd get resolved in a later update, without having to say anything about it, and I was wrong about that.

Any idea what's up, and how to get the tooltips to work as I would like them to?

If Firefox is started without an Internet connection on Linux (can happen on start up when the wifi isn't connected yet), the browser continues to refuse to connect to all webpages (unable to connect). It needs to be killed and restarted to work. Offline mode is not ticked. If offline mode is manually ticked and unticked it makes no difference. Ticking offline mode and retrying doesn't work and offline mode is automatically unticked. In the current version of OpenSuSE this is happening on every restart (possibly wifi is getting started a bit later), and it is also reproducible if manually started while disconnected from the wifi.

Hi All I have firefox 123.0.1 and don't have widevine! my OS is NetBSD 10 what's the best/easy'ish way to add this as channel 4 & 5 UK broadcaster require widevine installed and I can't find in the add-ons widevine!!!!

Hi, I watch specific streaming live show on YouTube every week. Unfortunately, I always have to play it in non-Firefox browser, because the video freezes every couple minutes, while audio track is still playing in the background. Based on the comments from the stream chat, other people have this issue too. Why? How to fix it? It is annoying. Internet connection is ok. Other browsers no issue. OS Linux Mint 20 Ulyana 64-bit Kernel Linux 5.4.0-172-generic x86_64 MATE 1.24.0 Mozilla Firefox 123.0 (64-bit)

Hello there. I'm used to pressing Super(Win key) + Grave(`) to type "`" because the Grave key itself is a global shortcut for opening the terminal window. It works as expected in the other applications, but not in Firefox input fields. If the site is capturing the key presses, it will handle the super + key as usual. For example, GitHub will surround the selected word with ` symbols on grave key press. This problem is not limited to super + grave, but any other letter. For example, Super + q is expected to produce the letter "q", but in Firefox it produces nothing.

I'm trying to identify why the Super + key behavior in Firefox is different from other systems and if I should open a bug or not. Maybe this is the same bug as https://bugzilla.mozilla.org/show_bug.cgi?id=1626609. Thunderbird has the same problem.

Firefox: 123.0.1

I saw a message that my Add-ons were disabled, and when I checked the Add-ons Manager , each of my many Add-ons had a message similar to: "1Password – Password Manager could not be verified for use in Firefox and has been disabled. "

Some searches in the forums suggest that that this can be caused my a certificate at Mozilla expiring, I seem to be the only one with this issue at the moment. All of my Add-ons came through the Mozilla store .

I am using version 123.0.1 (64-bit) on OpenSUSE Leap 15.5, and as far as I can see all of my updates are current (and from the official sources.)

What should I do next? I expect I need to wait for a certificate update or something at Mozilla, but if/when that happens how do I verify it did and re-enable my add-ons?

UbuntuStudio 22.04 uses the Firefox Snap package by default. The latest automatic update does not display pages correctly in normal mode, but does work correctly on Safe Mode. Snap.io lists only the latest version of Firefox so I was unable to ask snap to revert to the previous release (prior to 5 Mar 24) and by the time I had tried to investigate the previous version was no longer cached. I did not see a way to force a fresh download of firefox from the latest channel on snap.io.

I tried the snap beta channel for v124, but that exhibited the same problems.

I tried adding a symbolic link to colors.css after seeing firefox complaining that it could not be found when started from the command line. That removed the error/warning message but did not clear the problem with normal mode.

I use the en-GB locale extension only. The technical details about my PC are as follows:

• Operating System: Ubuntu Studio 22.04
• KDE Plasma Version: 5.24.7
• KDE Frameworks Version: 5.92.0
• Qt Version: 5.15.3
• Kernel Version: 6.5.0-25-lowlatency (64-bit)
• Graphics Platform: X11
• Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
• Memory: 30.5 GiB of RAM
• Graphics Processor: RAPHAEL_MENDOCINO

I have now downloaded v123 and installed it in my local home directory, and that version is working well. I have removed the firefox channel via snap. It is likely to be a fault in the construction of the snap for v123 that was not present for v122 prior to 5 Mar 24.

When you add a new bookmark to a folder it's added at the end of the existing list.

Is there a way to make Firefox add it at the top of the list, instead?

I found an old answer, but, sadly, the extension granting my wish is no longer.

Also, I already know about sorting, but it's not what I need, because I'm doing a lot of manual bookmarks reordering and sorting will nullify it.

Thank you :)