With Firefox discontinuing the use XUL overlay it raises concerns that Selenium IDE requires this overlay to function. Can anyone confirm one way or the other?
Asked
Active
Viewed 546 times
0
-
I'm not sure if this is the right place to ask something like this... – Matías Fidemraizer Feb 18 '17 at 12:34
-
Asking for an alternative is explicitly off-topic for Stack Overflow: "Questions asking us to **recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic** for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it." Given that your question does not require that sub-question, I have edited it out. – Makyen Feb 18 '17 at 15:54
-
@Makyen apologies and thank you :) I have only been on stakoverflow for about 2 weeks :) – Brainles71 Feb 19 '17 at 01:04
-
To close voter(s): This is about a topic that is included as on-topic under ["software tools commonly used by programmers"](http://stackoverflow.com/help/on-topic). Thus, it is on-topic for Stack Overflow. – Makyen Feb 19 '17 at 01:43
1 Answers
5
Selenium IDE is definitely an overlay/XUL based add-on. It contains an instal.rdf file and chrome.manifest file which uses the overlay directive.
Mozilla has stated that all types of extensions, other than WebExtensions, will be disabled in the near future. They have stated that the target for this is the 2017-11-14 release of Firefox 57. This deprecation may include complete themes, which they have stated "we will provide more details on what’s coming for themes very soon". That XUL based extensions would be deprecated was announced on 2015-08-15. The fact that they would be disabled in Firefox 57 (late 2017) was announced on 2016-11-23.
Mozilla has previously stated that such add-ons will not be explicitly disabled in Firefox Developer Edition and Nightly. However, a primary reason for deprecating such add-ons is that Mozilla wants the freedom to change the underlying Firefox code without worrying about add-on compatibility, other than WebExtensions. Thus, Firefox may change such that the features such add-ons rely upon are no longer available. Another alternative would be to use an Extended Service Release (ESR) version of Firefox. Firefox ESR 52 will be the current ESR at that time. My answer to "How to develop legacy Firefox add-ons in the future?" has more detail about possible options for continuing to use legacy add-ons.
I have not seen anything from Selenium IDE describing their plans for this change.
