new bug with full screen, similar to bug 1763981
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: frtz45, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
go to full screen e.g. in Youtube
Actual results:
first time you go full screen, it is not completely full screen (desktop visible on top and left of screen). If you go back to normal screen and then back to full screen it is OK. This happens only with Firefox, not with Librewolf or MS Edge.
Expected results:
full screen first time
User Agents says Windows 10, but with windows 10 there was no problem. Problem occurred after upgrade to W11
|
||
Updated•25 days ago
|
|
||
Comment 2•25 days ago
|
||
Hey frtz45, thanks for the bug report.
Can you try running mozregression to see if you can determine when the bug was introduced? In case you haven't used it before, there is a video at that link that explains how to use it -- you just need to specify a date when you believe there was no bug, and then check the versions of Firefox that it downloads and executes to see if they show the bug. It sounds like you've always seen this since switching to Windows 11, so you'll need to pick a date before you did that. I don't know when that was but I'd suggest starting from at least a year ago if you don't know what date to choose. Then you can just paste the output (including the pushlog_url if one is found) that it gives into this bug. Thanks for the help!
Hi David,
I tried my best to run mozregression as best as I could understand, but I am afraid I am not very good at this. The result I will paste here.
I upgraded windows 10 to windows 11 about one week ago, however in the report it still says it is W10 I am running.
I am 100% sure that this bug didn't exist two weeks ago under W10, but immediately after the upgrade to W11 it existed.
Strangely enough I have no problem with Librewolf or MS Edge. So thyis is all I can tell you.
The process of running mozregression and the video are difficult for me, but below is something I hope is of use to you.
platform: Windows-10-10.0.26100-SP0
python: 3.10.11 FROZEN (64bit)
mozregression: 6.3.0
message: PermissionError: [WinError 5] Toegang geweigerd: '\\?\C:\Users\ZAAK\AppData\Local\Temp\tmp_5z4lrui\firefox\firefox.exe'
traceback: File "mozregui\bisection.py", line 268, in set_verdict
File "mozregui\build_runner.py", line 81, in finish
File "C:\Program Files (x86)\mozregression-gui_internal\mozregression\launchers.py", line 332, in cleanup
remove(self.tempdir)
File "mozfile\mozfile.py", line 272, in remove
File "mozfile\mozfile.py", line 218, in _call_with_windows_retry
File "mozfile\mozfile.py", line 174, in _call_windows_retry
File "shutil.py", line 750, in rmtree
File "shutil.py", line 615, in _rmtree_unsafe
File "shutil.py", line 620, in _rmtree_unsafe
File "shutil.py", line 618, in _rmtree_unsafe
|
|
||
Comment 4•24 days ago
|
||
Thanks frtz45, all of this takes time so I'm glad you stuck with it. It looks like mozregression wasn't able to determine what was going on. Here's something easier to try: Can you download Firefox Nightly and see if you can reproduce the problem with it? There are fixes in that build that aren't yet released. If the problem is still there then we might need to try recording a log, but that's somewhat advanced, so let's try Nightly first.
sorry to say that running the beta version of Firefox didn't solve the issue.
However if I start Firefox in safe mode it doesn't have this problem.
Now you would probably say that it has something to do with my extensions, plugins or themes, but if I switch them all of I still get the same issue.
As I said, last week I was running windows 10 and Firefox worked fine. Only after upgrading to W11 the issue with Firefox occurred.
So I still assume there must be something between Firefox and W11.
If it is not a Firefox bug, but something on my PC, I simply have to live with it, I guess.
I just wanted to report this bug and I regretfully don't have the skills to run all kind of tests.
Problem for me is that I am willing to switch to a fresh profile in Firefox and I do know how to import my bookmarks, but I also want to import the links I have put on my homepage AND the exceptions I set in Cookies and Site Data. (settings > privacy&security > manage exceptions). I have my Browser Privacy set to 'strict' , so all cookies are deleted when I close Firefox except for the ones I have in 'Exceptions'
If I am the only one in the world with this, you could help me if you can tell me where I can find my 'homepage' and 'exceptions' folder in my profile folder. I am then able to copy and paste those in a new profile.
|
|
||
Comment 6•23 days ago
|
||
That's fine frtz45. Thanks for putting in the effort.
If you ran Firefox Beta instead of Firefox Nightly then you won't have gotten all of the fixes but you will eventually -- in a couple of months when they go to the Firefox release. But, if Safe Mode is working then the issue is not likely to be something I had considered. It sounds like you have a lot of customizations that could be involved. One last thing you could do that might help is go to about:support in the browser and paste the contents from there into a message here. That will tell us more about your setup.
As for creating a new profile with homepage and site data exceptions, you can find all of the contents of your profile by going to about:profiles in the browser and clicking to open the folders for the specific profile in question. I don't know which files in there are related to those topics, or if it is possible to just copy them into a new profile, but you could try. If you need help with that, you may have more luck asking at support.mozilla.org.
sorry, misunderstanding on my side: I did run Firefox Nightly, with the results I reported previously. I thought Nightly was the beta version of Firefox.
The about:support is a huge file, 37 pages, and I'm not sure it doesn't contain privacy-sensitive information. So I'd rather not share that on the internet, if you don't mind.
Thanks for the tip on where to ask my question about the homepage file! That might be a solution to this for my problem.
Hope you find something without my help.
|
|
||
Comment 8•22 days ago
|
||
No problem. Thanks for the report. FYI, about:support is the support diagnostics for the browser, so it has no private information, although it obviously does have some identifying information like the type of CPU. And emailing it works just as good.
Hi, if I am able to send the support diagnostics by mail, I will do so. But I copied and pasted it in Word and it's a document of 37 pages.......
And how do I send it? I don't have an e-mail address to send it to. Willing to send it to you, not paste it here.
|
Reporter | |
Comment 10•21 days ago
|
||
finally solved this issue by uninstalling Firefox, deleting all files I could find in Program Files, Program Data and AppData.
Freshly installed Firefox, imported Bookmarks with Firefox Sync. Then it took me quite some time to get all the Bookmarks working again and on the homepage. For instance you have to manually fill in the exceptions which cookies are always allowed. And various other settings are not transferred with Firefox Sync, so it takes a lot of time.
But now I am glad to say that it all works. So from my side this ticket can be closed. Thanks for your help and patience.
|
|
Reporter | |
Comment 11•21 days ago
|
||
I was a bit quick with that: after restarting my PC the problem was back........ (I didn't change anything in Firefox).
So all the effort for nothing. I give up. Maybe someone else with the same problem is able to help you?
|
||
Comment 12•11 days ago
|
||
The severity field is not set for this bug.
:handyman, could you have a look please?
For more information, please visit BugBot documentation.
|
|
||
Comment 13•5 days ago
|
||
Thanks for the effort frtz45. We didn't get too far with the debugging so I can't really make any assurances but your problem could be related to some recent work around widget sizing that is still in progress but has had some recent important fixes. I'm thinking specifically about bug 1963886 and bug 1906740. You mentioned bug 1763981 being similar and that bug goes into a lot more detail. Some of the conditions there resemble some of the ones cleaned up by recent work. If the details are truly similar then maybe we will get lucky.
|
|
||
Updated•5 days ago
|
|
|
Reporter | |
Comment 14•5 days ago
|
||
(In reply to David Parks [:handyman] from comment #13)
Thanks for the effort frtz45. We didn't get too far with the debugging so I can't really make any assurances but your problem could be related to some recent work around widget sizing that is still in progress but has had some recent important fixes. I'm thinking specifically about bug 1963886 and bug 1906740. You mentioned bug 1763981 being similar and that bug goes into a lot more detail. Some of the conditions there resemble some of the ones cleaned up by recent work. If the details are truly similar then maybe we will get lucky.
good to hear that there might be a solution.
In the meantime I am using Librewolf, which doesn't have this bug.
Maybe you can compare the two and find what the differences are?
Description
•