Closed Bug 1869976 Opened 2 years ago Closed 1 year ago

sharepoint webpages keep reloading up to 10 times when opened with firefox

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Version:
Firefox 120
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: b.loeffler, Unassigned)

Details

Attachments

(4 files)

Report
178.15 KB, text/plain
Details
Log
178.33 KB, text/plain
Details
Mozregression_2019_01_01
26.30 KB, text/plain
Details
Bisection
21.05 KB, text/plain
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0

Steps to reproduce:

  1. Open firefox in the latest version.
  2. Access any sharepoint website
  3. Reload of the will happen multiple times

This is reproduced with at least 4 users here in my office (I did not check others since everybody has the problem I asked).

Actual results:

Multiple reload prohibits a work with the site.

Expected results:

No constant reload should happen.

Hello, thank you for the bug report!
Unfortunately I could not reproduce your issue. Would you be so kind as to answer a few questions so we can investigate this further?

Moving the Product to ‘Core’ and Component to ‘DOM:Core & HTML’. Please change if there’s a better fit, thank you.

Component: Untriaged → DOM: Core & HTML
Flags: needinfo?(b.loeffler)
Product: Firefox → Core

Hello,

yes of course I answer your questions:

  • It happens on all our sharepoint sites. But I can't provide a link, since you would need a access to our company sharepoint and that I can't grant you for security reasons.
  • I think it does not have to do something with the profiles, since many of my colleges have the same problem and we independently started to use firefox and everybody has the same problem since a couple of days or 1 to 2 weeks.
  • Yes it also happens with the todays nightly build.
  • Yes it also happens in troubleshoot mode.

Thank you for your support.
Please tell me, if I can provide you anything else. Like a automated log from firefox when the issue occurs or something like this.

Flags: needinfo?(b.loeffler)

This might be a bit much to ask of you but one thing that you could help out with is trying to find what changed in Firefox using the tool mozregression. This tool takes a start date and and end date and iteratively tries different versions of Firefox to try to find where an issue was introduced. Since you know that it started behaving this way a couple of weeks ago, the time span to be tested would be just that. Since we cannot test against your sites this would be extremely helpful.

Flags: needinfo?(b.loeffler)
Attached file Report —
Hello, no problem at all. I'm happy to help as much I can. I used the tool and tested the versions. Here is the Bisecting report:

Also:

Tested mozilla-release build: 1378542b (verdict: g)
Tested mozilla-release build: 4aab41de (verdict: b)
Tested mozilla-release build: cf44e1e4 (verdict: g)
Tested mozilla-release build: 33c2aa88 (verdict: g)
Tested mozilla-release build: cc4649d5 (verdict: b)
Tested mozilla-release build: a2b9b84d (verdict: g)
Tested mozilla-release build: e245ca21 (verdict: g)

Flags: needinfo?(b.loeffler)

Thank you so much for your help. This is looking very promising!

Right, and at the end mozregression printed a link to a regression range. If you could paste that here it would be very helpful. It might be either 4aab41de or cc4649d5 that introduced the bug, but I can't tell, but the regression range will.

Flags: needinfo?(b.loeffler)

Where is this printed? I copied the whole log. Im affraied I have to do this again since mozregression cant store anything...

Flags: needinfo?(b.loeffler)

Here is the updated information:
Bisecting on mozilla-release [d6fae7c7 - 00d267e5]
pushlog_url: https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=d6fae7c7a0292b8c5670bbb427b9402b82e0ecaa&tochange=00d267e5882dfc433719d7f9a817aacbeee246ea
repo_name: mozilla-release

Tested mozilla-release build: b8f0d32a (verdict: b)
app_name: firefox
build_date: 2023-11-06 17:31:05.701000
build_file: C:\Users\BenjaminLoeffler.mozilla\mozregression\persist\b8f0d32ac6a5-shippable--mozilla-release--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GkTd7tSfTVmu3a8NSbfucA/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
changeset: b8f0d32ac6a5c34db8692ed382c3018e6309ea09
pushlog_url: https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=d6fae7c7a0292b8c5670bbb427b9402b82e0ecaa&tochange=b8f0d32ac6a5c34db8692ed382c3018e6309ea09
repo_name: mozilla-release
repo_url: https://hg.mozilla.org/releases/mozilla-release
task_id: GkTd7tSfTVmu3a8NSbfucA

Tested mozilla-release build: 4aab41de (verdict: b)
app_name: firefox
build_date: 2023-10-08 22:43:38.969000
build_file: C:\Users\BenjaminLoeffler.mozilla\mozregression\persist\4aab41de72b5-shippable--mozilla-release--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/VsERITTXTTaJkRjAl2ZAVw/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
changeset: 4aab41de72b5537366cc747d19f2f1a1f8eec0a1
pushlog_url: https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=d6fae7c7a0292b8c5670bbb427b9402b82e0ecaa&tochange=4aab41de72b5537366cc747d19f2f1a1f8eec0a1
repo_name: mozilla-release
repo_url: https://hg.mozilla.org/releases/mozilla-release
task_id: VsERITTXTTaJkRjAl2ZAVw

Tested mozilla-release build: cc4649d5 (verdict: b)
app_name: firefox
build_date: 2023-09-18 18:17:25.414000
build_file: C:\Users\BenjaminLoeffler.mozilla\mozregression\persist\cc4649d51632-shippable--mozilla-release--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Vxmsr1v_R0eRTjX0yL87Qg/runs/1/artifacts/public%2Fbuild%2Ftarget.zip
changeset: cc4649d51632dc5ddec2910bf6feed3a72331206
pushlog_url: https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=d6fae7c7a0292b8c5670bbb427b9402b82e0ecaa&tochange=cc4649d51632dc5ddec2910bf6feed3a72331206
repo_name: mozilla-release
repo_url: https://hg.mozilla.org/releases/mozilla-release
task_id: Vxmsr1v_R0eRTjX0yL87Qg

Tested mozilla-release build: e245ca21 (verdict: g)
app_name: firefox
build_date: 2023-09-12 03:40:30.567000
build_file: C:\Users\BenjaminLoeffler.mozilla\mozregression\persist\e245ca2125a6-shippable--mozilla-release--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/OvPIYO3TSOSFfie6qNS0rw/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
changeset: e245ca2125a6eb1e2d08cc9e5824f15e1e67a566
pushlog_url: https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=e245ca2125a6eb1e2d08cc9e5824f15e1e67a566&tochange=cc4649d51632dc5ddec2910bf6feed3a72331206
repo_name: mozilla-release
repo_url: https://hg.mozilla.org/releases/mozilla-release
task_id: OvPIYO3TSOSFfie6qNS0rw

Attached file Log —

Again, thanks for the help, this is invaluable!

I think we're stuck on the release channel of Firefox. The regression range we get is this, and that's still a bit too large.

I've mapped the commits on the release channel to the corresponding in the nightly channel, and maybe we could try testing on nightly directly if you're still able to help out?

I guess that you've been running mozregression from the console since you've been getting logs. In that case the command that I want you to run is:

mozregression --good c6981d9b3b12732164d6ba7e5b0ca63abf70021b --bad 7660099b8e3ed10ff50c0147736faf997dd33708

and then attach the report as you've done above.

Again, many many thanks for helping out.

Flags: needinfo?(b.loeffler)

Hello,
no problem at all!

Unfortunately the good/bad range is incorrect. The first version that opened had the issue:

Here is the tool output:
C:\Program Files (x86)\mozregression-gui>mozregression --good c6981d9b3b12732164d6ba7e5b0ca63abf70021b --bad 7660099b8e3ed10ff50c0147736faf997dd33708
0:00.63 INFO: bits option not specified, using 64-bit builds.
0:02.10 INFO: 7660099b8e3ed10ff50c0147736faf997dd33708 is not a release, assuming it's a hash...
0:03.53 INFO: c6981d9b3b12732164d6ba7e5b0ca63abf70021b is not a release, assuming it's a hash...
0:03.59 INFO: Getting mozilla-central builds between c6981d9b3b12732164d6ba7e5b0ca63abf70021b and 7660099b8e3ed10ff50c0147736faf997dd33708
0:07.20 INFO: Testing good and bad builds to ensure that they are really good and bad...
0:07.20 INFO: Downloading build from: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/WBPI-fV9RYaLmxS3ZtBxcg/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
===== Downloaded 100% =====
1:18.16 INFO: Running mozilla-central build built on 2023-07-28 06:39:43.499000, revision 36ce680e
1:19.99 INFO: Launching C:\Users\BenjaminLoeffler\AppData\Local\Temp\tmpawtivqhc\firefox\firefox.exe
1:19.99 INFO: Application command: C:\Users\BenjaminLoeffler\AppData\Local\Temp\tmpawtivqhc\firefox\firefox.exe --wait-for-browser -profile C:\Users\BENJAM~1\AppData\Local\Temp\tmp8pqmg1ih.mozrunner
1:20.03 INFO: application_buildid: 20230728043646
1:20.03 INFO: application_changeset: 36ce680ea81ccb2f123f0f6831596185e6ea4e83
1:20.03 INFO: application_name: Firefox
1:20.03 INFO: application_repository: https://hg.mozilla.org/mozilla-central
1:20.03 INFO: application_version: 117.0a1
Was this integration build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry' or 'exit' and press Enter): bad
5:46.53 ERROR: Build was expected to be good! The initial good/bad range seems incorrect.

Flags: needinfo?(b.loeffler)

Oh, that was strange. I guess that means that the regression window isn't where we think it is.

Alright, I know this is a bit much to ask (there will be more steps), but could you try mozregression --good 2023-01-01? It won't be that many more steps, but we're trying with a regression window that should be significantly large so that it should contain the problem.

Flags: needinfo?(b.loeffler)

Its getting even stranger.
6:09.73 ERROR: Build was expected to be good! The initial good/bad range seems incorrect.
Even the nightly of the 2023-01-01 has the issue with the page reloads of sharepoint sites. This does not happen with some later releases that year (like I tried in the mozregression linked here).

I also tried mozregression --good 2022-01-01
Its the same. The nightly even from 2022 reloads the sharepoint page up to 6 times.

But only the first time the website is accessed. When I reload the page afterwards manually or when I access it in a new tab. Then its fine.
When I clear the browser cookies and access the site newly (loging needed for sharepoint), then the reload occurs again.

The current latest release version of firefox behaves like this:
reload of shrepoint pages after access. Then if stable and the site is accessed again in a new tab -> reloading happens again.
So the release version behaves different than the nightly.
From the mozregression done in this ticket I can tell 100% that the "good" releases in the regression are really good, so no reloading at all.

Flags: needinfo?(b.loeffler)

Edgar, I didn't get very far triaging this. Leaving an ni, since we've gotten lot's of help from the reporter and you're doing triage next week to make sure we don't drop this when we have some kind of momentum.

Flags: needinfo?(echen)

Thank you for your helps!
I have a question regarding the nightly behavior.

(In reply to b.loeffler from comment #13)

I also tried mozregression --good 2022-01-01
Its the same. The nightly even from 2022 reloads the sharepoint page up to 6 times.

But only the first time the website is accessed. When I reload the page afterwards manually or when I access it in a new tab. Then its fine.
When I clear the browser cookies and access the site newly (loging needed for sharepoint), then the reload occurs again.

Does the latest nightly behave the same as you mention above, e.g. you got same buggy behavior on both latest nightly and the nightly from 2022.
Could you kindly to try even more early version of nightly, e.g. 2019, if possible?

Flags: needinfo?(echen) → needinfo?(b.loeffler)
Hello, I tried the nightly from today: 123.0a1 (2024-01-07) Its the same behaviour with constant reloads for a time and then its fine. When I then reload the page, the reloading starts again for a lot of times. I did the mozregression from 2019 on forward:

One question regarding the nightly and the release:
The nighly does not work from the 2020-07-22 on forward, but the release build works till October/November 2023.
Just out of curiosity, how is this possible? Are there maybe features, that are merged very late into the release build?

Thanks again for all your help! I can tell you guys are one of the best support teams out there! You care and you help, and that is extremely valuable these days!

Flags: needinfo?(b.loeffler)

The nighly does not work from the 2020-07-22 on forward, but the release build works till October/November 2023.
Just out of curiosity, how is this possible? Are there maybe features, that are merged very late into the release build?

So it sounds like around 2020-07-22, we changed something on Nightly and this didn't go to release till October/November 2023. It's possible for a feature takes a long time :)

What if you do mozregression --good 2020-06-01 --bad 2020-07-23? Does this reveal the changeset that cause the regression?

Flags: needinfo?(b.loeffler)
Attached file Bisection —
Thanks for this information! I did again the bisection:

Hello everybody,
any updates so far regarding this problem?
Can you reproduce it with an own sharepoint space?
Best regards,
Benjamin

Flags: needinfo?(b.loeffler)
Severity: -- → S3

Hello everybody,
can you give me maybe an update?
We still can't really work with our sharepoint intranet and more and more colleagues switch to different browsers :(
I would really like to give them some updates.
Can you reproduce the issue on your side? Or will no action be taken?
Thanks for the information

Flags: needinfo?(hsivonen)

I don't have access to Sharepoint. Hsin-Yi, who should take a look?

Flags: needinfo?(hsivonen) → needinfo?(htsai)

Hi, sorry about being slow on this bug. We are trying to test it on sharepoint now to see if we can reproduce it from our end.

In the meantime, do you mind to use http://profiler.firefox.com/ to collect a profile for this?

  • Just use the latest nightly, install that addon, make sure it's Nightly setting.
  • Then click Start Recording, use the browser to reproduce the issue and click Stop Recording lastly.
  • After that a profile page will be opened automatically, there's Upload Local Profile button on the right, use that to upload the profile and paste the link here. Note that, it'll include screenshots by default, you might want to disable that when uploading to avoid leaking sensitive information. However including the screenshots will be helpful for us.

Thanks

Flags: needinfo?(htsai) → needinfo?(b.loeffler)

That's fine, the problem fixed itself somehow. No more reloads on my side.
I provided all the information regarding the versions it occurs in the mozregression so that you could maybe track this down if its of interest for you.
If its not fixed intentionally, then maybe you should have a look into it anyway. A Bug that's there and then unintentionally went away sounds suspicious to me and may occur again in future.
But right now we don't have any problems, so we are happy with everything.

Unfortunately I can't now invest any more time in this and since its seems to went away we are happy for now. Plus I can't reproduce it now with the latest release anyway.

Thanks for all your support and reactivity!
Best regards
Benjamin

Flags: needinfo?(b.loeffler)

Thank you very much for the patience and assistance, Benjamin.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME

Hello,
unfortunately I have to raise this again. With the latest updates the behaviour is back again.
Sharepoint reloads multiple times. I get the first requests from my team that they have problems using sharepoint with firefox.

So please get this ticket reopened and worked on again. Thanka

Flags: needinfo?(sefeng)

Hi, do you think you can try my steps in comment 23? Ideally we'd like screenshots if possible. And feel free to send an email to me (sefeng@mozilla.com) if you don't feel comfortable sharing it publicly.

Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(sefeng) → needinfo?(b.loeffler)
Resolution: WORKSFORME → ---

Hello,
thank you very much for this fast reply!
I did upload the profiler record:
https://share.firefox.dev/4eXMXK8

Now the problem seems to got worse. Even after 2m40s the reloads did not stop.

If I can be of any more help, feel free to ask. Thanks again and best regards,
Benjamin

Flags: needinfo?(b.loeffler)

I see the page often get redirect to https://envea.sharepoint.com/_forms/spfxsinglesignon.aspx#error=invalid_client&error_description=..... By doing the research, I found this article https://www.eliostruyf.com/browser-refreshing-sharepoint-page/.

Do you mind try the listed solutions there and see if it helps?

Flags: needinfo?(b.loeffler)

Hello Sean Feng,
thank you so much, you just made my day!

I checked out the article. The think with the third party cookies makes sense. So this is just a configuration problem.
With the Solution2 of the article sharepoint now works at my machine :)
Our IT will check out how to configure sharepoint to fix the problem global in our company.

So this seems not to be a BUG but simply a stricter security setting. Could this maybe documented somewhere for firefox in some kind of FAQ or other documentation? You could just link this article you send somewhere so more people find it.
I bet others will have the same problem and trigger you guys.

So with this support ticket we are finished I think :) A correct handling of this behaviour is possible and it works.
From my point of view you can close this ticket.

I want to express my deepest gratitude to all of you. Such active support with so many people involved cannot be taken for granted. It's really worth a lot. Thank you!

Best regards,
Benjamin

Flags: needinfo?(b.loeffler)

It was our pleasure to help you! Thanks for being a Firefox user and we really appreciate the bug report!

I'll ask our team internally about documenting it somewhere, thanks for the suggestion!

Best,
Sean

Status: REOPENED → RESOLVED
Closed: 1 year ago → 1 year ago
Resolution: --- → INVALID

Hello,

I want to dig a bit deeper into the root cause of the reloading issue here.

Do you have any strict cookie opinion enabled? For example, have you enabled ETP strict mode or enabled blocking all third-party cookies in ETP Custom mode? Also, I am wondering on which Firefox channel you see the reloading issue. Is it the Nightly channel? Thanks.

Flags: needinfo?(b.loeffler)

Hello Tim,

I encounter the reloading issue with the Nighly Build as well as with the Release (Version 128.0).
regarding the cookie options: Im not sure, I think the most of use use the default settings with firefox and encounter the problem. If you mean sharepoint: There I'm not sure since im not a sharepoint admin. But I think the most stuff is default as well since they did not highly customize it.

Flags: needinfo?(b.loeffler)

What can I provide you to answer your question regarding the options? Is this not in the profiling record I uploaded?

You can provide the troubleshooting info on the about:support page. If you feel uncomfortable to share it publicly, you could send it to my email address. Thanks.

Hello Tim,
I just send you a mail with the troubleshooting info as attachments. Thanks.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: