Sometimes a file name box is read-only and you can't type in it. If you click the "Browse..." field then a file picker window should open where you can select the file. You can also try to drag a file and drop it on the input field.

• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file

Actually I _can_ use the Browse. The file name box in the past let me type in a file name. Now if I try to type it turns into garbage. e.g. If I type: I'll it might say something like %uwx. We even checked with a different keyboard and the problem remains. My files are fairly extensive, so Browse can be a lot to wade through.

You can't type in a file input element. If browsing takes too long then use drag and drop, that should work as a workaround.

These work-arounds are just that, better than not at all, but not as good as it had been when I could type the name of the file sought.

I hesitate to mark it solved as it can be a large amount of files to wade through. Prior to this I could type the file name.

It was suggested by the Microsoft (upper level) technician that I send a screenshot here of what's happening. Microsoft has pretty much tried everything short of working with my preferred choice of browser, Firefox, since the problem doesn't exist on Edge. I don't really care that Chrome also has the problem. I also have a large enough quantity of Downloads and Documents that scrolling is not really the answer.

If there's more information needed, please let me know. I'm only sending this in the hope it reveals information possibly related to a recent Mozilla/Firefox update since it's possible it came from that. It does _not_ seem to be from a Windows update.

There are some new glitches to this story. Today I replaced my keyboard only to find the problems again don't happen on Edge, but on Firefox there now are two keys that don't work properly: the key that is both the number "two" & an "at" symbol and the key for a "question mark" and a "slash." For those two keys even the onscreen keyboard produces the same results.

• For the number "two" & "at" I get "t" & "T"
• For the "question mark" and "slash" I get "I" & "i"

The library where I work no longer tends to use Firefox because it has found reliability problems. I have long preferred Firefox for its Open Source and its dedication to privacy. Unfortunately these two keys _are_ fairly unavoidable and it looks like I will be switching reluctantly to Edge. I do hope the developers find out what is happening and let me know when I can return to a keyboard that functions properly as there seem to be no "work arounds" for non-functioning keys.