We created a Connector profile for Firefox with "Use Javascript to find controls" that previously worked as a proof of concept. It is now close to implementation and the Connector no longer works with Firefox. Firefox is still configured as per the documentation, and the debug server is starting on port 6000, according to the Windows Task Manager. The profile appears to work but it does not appear to be passing any data. When trying to create a new profile with Firefox it does not highlight and recognize any fields. IE works, as does Chrome. Are there other settings within Firefox that need to be changed that are not listed in the Admin doc for Connector?
Question
Question
Answer
APPROVED ANSWER
replied on March 5, 2020
Hi Jason,
Thanks for reporting this, and I apologize for any inconvenience it may have caused. We can reproduce the issue and have filed a bug #229481. We'll look to fix this issue in the next hotfix/release.
In your case, is that possible to use other browsers like Chrome?
0
0
replied on March 9, 2020
The application we are using in conjunction with the Connector is standardized upon Firefox as are the desktops. However if we have no other alternative we may be able to temporarily deploy Chrome until a fix is released.
1
0
replied on March 10, 2020
•
Show version history
If you cannot deploy Chrome successfully, you can open a support case by your reseller and request a specific hotfix of this Firefox issue, but it will take us some time to prepare the specific hotfix.
0
0
Replies
You are not allowed to reply in this post.
You are not allowed to follow up in this post.