Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

A specific website wont redirect to their ADFS website.

  • 3 odgovora
  • 0 ima ovaj problem
  • 18 prikaza
  • Posljednji odgovor od b.debakker

more options

We use Firefox ESR for along time in our organisation but with the last update, a specific page wont redirect to the ADFS page. In the latest normal version of Firefox it works and also other browser but not in ESR.

The webpage is https://rx-base.nl/ and https://preprod.rx-base.nl/

We are using the latest version of ESR. It gives a blank page with in the console a error:

Uncaught (in promise) TypeError: Fout bij het oplossen van modulespecificatie ‘@rxbase/root’. Relatieve modulespecificaties moeten beginnen met ‘./’, ‘../’ of ‘/’.

Please advise on what to do.

We use Firefox ESR for along time in our organisation but with the last update, a specific page wont redirect to the ADFS page. In the latest normal version of Firefox it works and also other browser but not in ESR. The webpage is https://rx-base.nl/ and https://preprod.rx-base.nl/ We are using the latest version of ESR. It gives a blank page with in the console a error: Uncaught (in promise) TypeError: Fout bij het oplossen van modulespecificatie ‘@rxbase/root’. Relatieve modulespecificaties moeten beginnen met ‘./’, ‘../’ of ‘/’. Please advise on what to do.

Izabrano rješenje

So what I discovered is that enabling a feature called import maps fixes this.

In particular, setting this pref:

dom.importMaps

to true.

Do you use policy to manage Firefox?

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (3)

more options

That's quite odd. I'll need to debug and figure out what's going on.

I am able to recreate the behavior, and I'm wondering if it used to be broken on regular Firefox and got fixed at some point.

Also, FYI, we're releasing a new ESR in a few weeks and it will work there.

more options

Odabrano rješenje

So what I discovered is that enabling a feature called import maps fixes this.

In particular, setting this pref:

dom.importMaps

to true.

Do you use policy to manage Firefox?

more options

Hi Mike, that indeed solves the problem. We use policys indeed so we added it to the preferences (in JSON)

{ "dom.importMaps.enabled": { "Value": true, "Status": "locked" } }

Hopefully it doesnt break any other website :) , thanks for the solution!

Izmjenjeno od b.debakker