Add firefox support
Closed this issue · 6 comments
This extension of sorts, righ now, doesn't work for firefox.
Hi @VatraXD
Firefox is my default browser and I work with the auto-type application (not an extension) all day long as I have to log literally hundreds of times into development environments for my job.
Please include the debug file created and relevant information like Firefox version and other details to try and catch what's wrong.
It seems a pretty generic error across the whole OS... what I gather is something is not right with your Firefox installation. The debug information tells me that is trying to grab the value from an object that it doesn't exist however there is an object reference and the apps asks the value.
BugZilla and StackOverflow do have a lot of hits pertinent to the error itself but nothing on the specifics of the accessibility object that triggers it.
If you want to try to create a clean profile, that will help a lot to see if is an extension that modifies the profile structure of Firefox or even better, if you can download a copy of the Portable Firefox and try there would be even better.
That way we can know where the issue comes from.
My firefox install is very new, only a few extensions, and userchrome.css, I tested in troubleshoot mode, which disables every extension. It still doesn't work. Not sure if userchrome.css could interfere with this application, neither if troubleshoot mode disables it.
I couldn't edit my other comment,
Troubleshoot mode disables userchrome.css, I attached the newest debug.txt.
debug.txt
I tried different computers and even a 32 bit version of Firefox but couldn't replicate the issue. However with the debug log I was able to identify where the error was triggering the alert and added some more validation.
While the problem is not exactly related to the Auto-Type app but something going on with your system (ghost in the machine kind of stuff), the extra validation will stop the error from triggering and continue to a point when the URL can be retrieved.
At the same time, the URL detection got some improvements, so thanks a lot for the bug report and hopefully the enhancements will keep the issue from affecting you.
Current release (v1.1.4) has now updated assets with this fix in place.