On 07/28/2020 Firefox released version 79 of the browser.
This version has an incompatibility problem with the Plugin of said browser.
The problem:
It does not allow the inspector or activities like Clic to interact with objects within an iFrame.
This caused all my robots (6) to fail for the same reason.
Hi @JFEspanolito,
Thank you for information. Please remember next time that you can use UserVoice category for posting information about potential bug/improvement. Just click on Give Feedback on upper menu and then choose adequate tag for the product
We know it can impact the processes. But to be honest projects should be made in the way which could catch any type of unexpected behavior. Itâs one of the best practice I would say. You can use for example Re-Framework template which is able to catch errors and then you can define what action process should take in case if these. I would say that process development is not about building the solution at once but about constant iteration based on changes around the process
Ah, thank you for responding. I have not yet hit the level of proficiency required to catch âANYâ type of unexpected behavior. Thank you for pointing that out.
I will continue to try to improve.
So what you are saying is that if Firefox gives an error then the robot should use Chrome and if Chrome does not work then Edge? That would be a significant time increase in my workload covering events that might occur every 2-3 years
I think what he means is, if anything goes wrong in your processes, it should have ways to overcome⌠For example, in your try catch, include a verification that looks for this message that breaks your action and add a click to remove itâŚ
Adding a click to remove does not solve my problem. In order to have my robot finish I need to use another browser because actions are not executed in Firefox.
Interesting solution. I would prefer to wait for an updated plugin that works without the issue than to change up to 100 selectors.
Thank you for sharing.
Just to complete my thoughts. What I meant is exactly what @bcorrea said. I would like to add something to this. Most environments (at least all I had possibility to work on) have the policies which restricts any potential update of any application. Of course Iâm talking about the customers. Why is that? Exactly because it may provide to unexpected behaviors. Best practice in such cases is to have something what is called the Production and the Test environment. Once a while (depends on internal policies of the company) there are tests on non-production environments which are divided for couple parts like: os updates, software updates, hotfix deployment, DR tests, backups and so on. And if then no major problem occurs such updates are deployed on production. Why Iâm telling this? Because in IT world thereâs always something what can go wrong. Of course Iâm not trying to excuse the fact that firefox is not working just because I just wanted to point out that similar cases is just matter of time and good developer is developer who can predict such cases and prevent from them during development phase. So the solution like âI will wait until somebody fix thisâ is not a good solution.
Let me leave you guys with one sentence Iâd love to remind:
âThe computer was born to solve problems that did not exist before.â
~ Bill Gates