2042805 - www.roadcard.com.br - The page is stuck in a loading state after clicking on the "Entrar" button (login)

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P2)

Description

[Raul Bucata]

Environment:
Operating system: Windows 10
Firefox version: Firefox 151.0

Steps to reproduce:

1. Navigate to: https://www.roadcard.com.br/sistemapamcard/?loadGaScript=load
2. Insert any data into the login fields
3. Click on the "Entrar" button and observe

Expected Behavior:
The page returns an error message

Actual Behavior:
The page is stuck in a loading state

Notes:

• Reproduces regardless of the status of ETP
• Reproduces in firefox-nightly, and firefox-release
• Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/221810

Comment 1

[Raul Bucata]

Attachment: Chr vs FF

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Comment 3

[Ksenia Berezina [:ksenia]]

Wed May 27 2026 10:13:16 GMT-0400 (Eastern Daylight Time) error = TypeError: can't access property "f1", ofdb is null error in the console

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Note: both a user name and password need to be entered to reproduce the problem.

Comment 5

[Daniel Holbert [:dholbert]]

(In reply to Ksenia Berezina [:ksenia] from comment #3)

Wed May 27 2026 10:13:16 GMT-0400 (Eastern Daylight Time) error = TypeError: can't access property "f1", ofdb is null error in the console

Here's the relevant JS:

function executeF1() {
	console.log(new Date() + " executeF1 ");
	try {
		var loginType = 'PF';
		var accountParams = {  
			    param1: document.getElementById('login').value,
			    param2: document.getElementById('topazAplicacaoTipo').value,
			    param3: 'NAOSEAPLICA',
			    f10Param: 'NAOSEAPLICA'
		};
		ofdb.f1(loginType, accountParams, executeF1Pos, executeF1Error);

https://www.roadcard.com.br/sistemapamcard/includes/script/gas.js?4=4
ofdb here is indeed null in Firefox, but non-null in chrome.

Working backwards, we diverge from Chrome a bit earlier, here, where ofdb gets assigned:

function setOFDBWrapper(idSessao, sigla) {
	try {
		console.log(new Date() + " setOFDB - INIT");
		if (typeof OFDB !== 'undefined') { 
            ofdb = new OFDB(sigla, idSessao, []); 
        } else { 
            console.warn(new Date() +'Script do OFDB não foi carregado corretamente'); 
        }

In Chrome, typeof OFDB is "function" there, and ofdb = new OFDB( steps into some functionality in https://rdc.dnofd.com/ofdb/OFDB.js .

In Firefox, typeof OFDB is "undefined", because that script got blocked by Firefox's ETP settings.

Aha. So this is an ETP issue.

If I turn off ETP for this site, then the issue goes away (because the OFDB script gets unblocked).

Comment 6

[Daniel Holbert [:dholbert]]

(In reply to Raul Bucata from comment #0)

Notes:

• Reproduces regardless of the status of ETP

This^ does not match my experience, as I just noted. The issue goes away if I turn off ETP for this site.

Comment 7

[Daniel Holbert [:dholbert]]

Actually, in a brand-new fresh profile in latest Nightly, ETP does not block OFDB.js at all, and the site loads just fine.

But in release, I do still see OFDB.js being blocked. Maybe we (or Disconnect) have added an exemption that's made it into Nightly but not release?

Comment 8

[Daniel Holbert [:dholbert]]

Attachment: screencast showing the bug happening on release, due to ETP

Comment 9

[Daniel Holbert [:dholbert]]

sky, what's the correct way to triage/annotate WebCompat bugs that are due to ETP blockage (in default configuration)? (removing them from the "needs-diagnosis" bucket)

timhuang, do you know why I might be seeing this script ( https://rdc.dnofd.com/ofdb/OFDB.js ) blocked by ETP in release but not in Nightly? (default config in both) Do we use different disconnect lists there (or is Nightly using a more up-to-date-list), and do you know if there's a way to check the status of this script in this list, to confirm that this suspected-fix is on the way to release users?

Comment 10

[Tim Huang[:timhuang]]

It's because there is a recent update to move the domain "dnofd.com" from the analytics tracker to the content tracker. The list update hasn't touched the release channel. I can see if I can uplift the changes.

Comment 11

[Daniel Holbert [:dholbert]]

Thanks! As long as that's on its way to release in some form (whether uplifting or riding the trains), I think we can close this. Is there a bug associated with that change that we can mark this as depending-on / fixed-by?

Comment 12

[Tim Huang[:timhuang]]

Unfortunately, the changes happen on the delivery server. I've made the change on the server side, and it typically takes a day or two to deploy it to users. So, we can wait a day and verify whether the change fixes the issue, then close this bug.

Comment 13

[Daniel Holbert [:dholbert]]

This seems to be fixed now, as-expected per comment 12. I now get a "Incorrect username or password" message (as-expected), in Firefox 152.0.4 with a fresh profile, when following the STR here.