New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Require an id to be set in Firefox web extension manifests #6471
Comments
Ruby support landed in a25638d |
I guess now all the bindings except JavaScript work similarly. |
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 14 days with no activity. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
As mentioned in #6463 (comment):
Current client implementations
Here is how the ruby bindings handle web extensions without an id (it doesn't even look for applications.gecko.id):
selenium/rb/lib/selenium/webdriver/firefox/extension.rb
Lines 85 to 91 in 07a1874
The Java bindings looks for applications.gecko.id but does the same as the Ruby bindings in case it isn't set:
selenium/java/client/src/org/openqa/selenium/firefox/internal/FileExtension.java
Lines 141 to 155 in ba32c5b
The JavaScript bindings throw an error if applications.gecko.id is not defined:
selenium/javascript/node/selenium-webdriver/firefox.js
Lines 172 to 174 in 3e99112
The Python bindings, as proposed in #6463, exhibit the same behavior as the Java bindings:
https://github.com/motin/selenium/blob/add-python-client-support-for-webextensions-in-firefox/py/selenium/webdriver/firefox/firefox_profile.py#L333-L339
The text was updated successfully, but these errors were encountered: