Firefox Support Forum

At some point, I've noticed that certain behaviours expected to occur when pressing the Escape key no longer did. Those behaviours mainly involved triggering some Javascript, including functionality in keyboard-related extensions, such as Tridactyl. Browser-level functionality on the other hand, such as pressing Shift-Escape to open `about:processes`, or pressing Escape to close Search Suggestions when the URL input bar, continue to work as before.

Upon investigation, I found it is specifically the javascript Keydown event that isn't being registered, while the subsequent Keyup event still is. I used https://w3c.github.io/uievents/tools/key-event-viewer.html to test this.

I also found that starting Firefox in Troubleshoot Mode (Safe mode) doesn't resolve the issue. On the other hand, creating a new profile does.

I've looked at the modified settings in `about:config`; there's a lot, but nothing stands out as being related to keyboard input or javascript.

Can someone please help me find what is causing this?

hello. I have a reproducable issue with Firefox. If I use the touch keyboard on Firefox and then exit Firefox without without closing the touch keyboard, when I next start Firefox it only opens with a half view. if I close the touch keyboard first and then exit Firefox it opens as normal in a full screen view. it has nothing to do with either an extension or a theme. is there any way of ensuring that FF opens in full screen view if I forget to close the touch keyboard before exiting the browser? thanks in advance. PS: device is a Surface Pro 7 running Windows 11.

Hi, I get the below error message when trying to login to visma.net (for work).

json.parse unexpected character at line 1 column 1 of the JSON data

On this note I have a previous error, loggin in to this site that was fixed by a support member (• accessibility.blockautorefresh = false), but I have the above hurdle left. I can get past it by clicking backspace but thought there might be a better solution - maybe some other setting I can adjust similar to the first fix I got help with.

The web address for this error message shows as: https://api.home.visma.com/home/rest/sso/login

Kindly Eva-Marie

So, here's the story:

My browser crashed while watching a video and writing a particularly lengthy YouTube comment on it. Knowing that I have been able to recover in-progress Reddit comments after a crash from the sessionstore-backups so long as I was on the page at the time of the crash, I know that at least one site saves all in-progress comments to that, and I highly suspect that is where in-progress Wikipedia edits are kept, I (wanting as much data as possible for as good of a recovery chance as possible) immediately copied all my Profile files, totalling more than 1.6 GB, to a non-volatile folder.

As I had done before, I took the most recent sessionstore-backups file (dated to the exact minute of the crash), forced it through the Session History Scrounger to decompress it, and then mass-replaced the document's \ns with proper newlines in Notepad++, which used to make the file more readable.

This time, it didn't. They must have changed the json newline formatting used between at least late April and now. And more importantly, when I searched through the file for keywords I used in the comment, I couldn't find it. Simply, it appears that in-progress YouTube comments aren't stored in that file.

So, where are they stored? Are they in any vaguely human-readable file (or file that can with some ease be converted into something vaguely human-readable)? Can I somehow revive a "zombie session" using just archived Profile folder data to copy it out of? Or should I just give up and rewrite the comment from scratch?

NOTE 1: This is adapted from a previous post made with an associated account on Reddit. As I fear using Firefox until I get this problem resolved due to the possible loss in ability to recover other data if I do so, I figure that giving the problem more attention here would be beneficial in resolving it more quickly.

NOTE 2: Also, to clarify, I don't need to restore the session and have the comment re-appear; I'd be fine with locating it in a text editor or similar program so I could copy it back into the submission box once the session is restored.

I have the same issue as stated in https://support.mozilla.org/en-US/questions/1390122?page=3

How does it come that it is still present in 117? Why is there no official guide or warning about this issue? I am forced to use Portable 101 where there are no such bugs. The solution in the thread is unclear and points to Microsoft, which is ridiculous. The question is how to solve that Mozilla's bug?

Using Firefox 17.0.1 on MacOS Ventura 13.6 on my 2017 iMac I am unable to connect to the internet while using Private Internet Access (PIA) VPN. All was working normally until I installed MacOS Ventura 13.6 yesterday. The VPN works normally when using Chrome or Safari. I have tried changing my network proxy setting without any luck. The default setting is "Use System Settings", using No Proxy or Auto Detect Proxy doesn't help. I don't see a switch for Enable DNS over HTTPS. All works fine when the VPN is disabled. I tried deleting the VPN a couple of times then reinstalling but that didn't help.

What am I missing here? I have used this VPN for years without any issues & it worked on Firefox until I installed MacOS 13.6...... using 13.5 I had no problems. Any suggestions or thoughts would be appreciated.

Thanks...... Brad