You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once you go NaN, that's it. Clearing cache does not help. Manually entering a port number does not help. Pressing +1 does not help.
Changing portInput through console does not work. (Invoking +1 does work, as in it doesn't throw an error. It still stays at NaN)
Trying to edit the text area through the inspector doesn't work because it's not a text area, it's some weird flexbox fjavascript mess containing a bunch of events.
Changing the ID as such finally unlocked the +- buttons.
Though, it couldn't be changed through console for some reason. Inputting into the port box still didn't work until it was at a value other than NaN.
No, errors, nothing blocked in the network tab. Nothing blocked by uBlock Origin, nothing bugging out in console besides your average CSS. The scrips were simply never triggered. Even if manually invoked through console.
Don't really have any other debugging info, since none of the usual Firefox culprits like ETP seem to have been at play.
The text was updated successfully, but these errors were encountered:
Once you go NaN, that's it. Clearing cache does not help. Manually entering a port number does not help. Pressing +1 does not help.
Changing portInput through console does not work. (Invoking +1 does work, as in it doesn't throw an error. It still stays at NaN)
Trying to edit the text area through the inspector doesn't work because it's not a text area, it's some weird flexbox fjavascript mess containing a bunch of events.
Changing the ID as such finally unlocked the +- buttons.
Though, it couldn't be changed through console for some reason. Inputting into the port box still didn't work until it was at a value other than NaN.
No, errors, nothing blocked in the network tab. Nothing blocked by uBlock Origin, nothing bugging out in console besides your average CSS. The scrips were simply never triggered. Even if manually invoked through console.
Don't really have any other debugging info, since none of the usual Firefox culprits like ETP seem to have been at play.
The text was updated successfully, but these errors were encountered: