Can't login with firefox

[paulRenault]

Node-RED version: 0.19.5 (docker)
node.js version: v8.12.0
npm version: 6.4.1
Platform/OS: ubuntu 18.04
Browser: Firefox 63.0 (64 bits)

Uncomment the section "adminAuth" in the file "settings.js", use firefox.
Try to enter your password, the focus come back to the Username.

In the console there is the following error :

Une chaîne vide a été transmise à « getElementById() ».

I tried with chrome and its was working. The error is not in the console.

[knolleary]

Can you please provide the full error message from the javascript console? Are there any line numbers etc?

There is another user on the discourse forum who has reported some similar behaviour, but no-one has been able to reproduce.

Do you have any password managers or other extensions installed that may be trying to interact with the login form?

[paulRenault]

This is the full error. The error is in vendor.js 2:24487

No, this is the default firefox on ubuntu 18.04 without any extensions.

We just try with one of my colleague and he haven't the error with Firefox Quantum 63.0.1 on Windows.
On my laptop with ubuntu 18.10 and firefox Firefox Quantum 63.0, I haven't the error.

[knolleary]

So its just one browser on one operating system. Not sure how far we'll get debugging that unless someone is able to reproduce and dig into it for us.

[juggledad]

Works in OSX 10.13.6 with FireFox 63.0.1

[Kazuki-Nakanishi]

Works in the following environments.

Node-RED version: 0.19.5 (master branch)
node.js version: v8.11.2
npm version: 5.6.0
Platform/OS: Windows 8.1
Browser: Firefox 63.0.3 (64 bits)

Node-RED version: 0.19.5 (master branch)
node.js version: v10.13.0
npm version: 6.4.1
Platform/OS: Ubuntu 16.04.5
Browser: Firefox 63.0 (64 bits)

[vunhan]

Seems problem with GNOME on Ubuntu 18.04
I updated system to Ubuntu 18.10 then everything works.

[killua-eu]

I'm on GNOME/Ubuntu 18.10 and noticed, that focus stays in the password input field for only half a second. So in order to log in, i have to click into the password field and paste the password right away as typing it takes too long. Chrome is not affected. I'm using keepassXC on firefox.

[Just-another-pleb]

Hi.
I have nearly got it working.
On one machine it works, on another it doesn't.

To (maybe) help people following this,
could you maybe list the commands (or how) to get the versions of NR, NPM, JS etc.

Then the person can check all parts are "up to date".

Oh, just for the record:
On the machine I have these versions.
(I don't know why they come up as "crossed out" but it is cut/pasted from terminal)
pi@TimePi:/.node-red $ node -v
v8.12.0
pi@TimePi:/.node-red $ npm -v
6.4.1
Raspberry Pi Model B Rev 2

PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Raspberry Pi reference 2018-03-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 00013d7972122d1304aacda8fff5098f073ceb43, stage5

and node-red at V0.19.5

Logging in from:
Ubuntu 18.04 LTS
FF 64 (64 bit)
Problem persists.

But if I log into NR running on Ubuntu it works.

[Just-another-pleb]

Slight update.

Did better home-work this morning.

(Quick back story)
I have a VM running NR on Ubuntu. It is as clean as possible.
I load the VM and it works fine.
To the best of my knowledge it is Ubuntu 18.04.1 LTS.
Using FF 64 (64 bit) from THAT machine it works with passwords to log in to NR.
I haven't ACTUALLY logged in, but the problem of not being able to access the PASSWORD field no longer happens. So, "it works".
I have NR on a RPI. (Stretch).
Logging in from the VM to the RPI also works - and I HAVE logged in to the editor.
So that is a base line.

Back to THIS machine (Ubuntu 18.04.1 and with the same FF) it doesn't.

I know it is probably going to be "the proverbial" but I am not seeing what to do now to find the problem.

[Just-another-pleb]

Update - sorry for delay:

Though sounding cliche: It is now working.

I am using Ubuntu 18.04.1 LTS
NOT 18.1. Not saying anything against people who have it, but it would seem that is not part of the problem.

However, knowing my luck: It will make a lier of me in the not too distant future.

[killua-eu]

The problem disappeared for me as well. I guess it was a problem relevant to the specific ff build.

[knolleary]

Closing due to inactivity.