You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[π Feature]: JSpecify Nullness annotations for JavaΒ #14291
I suggest adding JSpecify Nullness annotations to the Selenium framework code.
These annotations allow you to specify which parameters and return values can be null.
I'm aware that information about potential null values are already placed in the JavaDoc, but using annotations will be transparent to IDEs and static code analyzers.
This will give developers better exposure of potential problems with their code in order to avoid NullPointerExceptions.
Using annotations will also improve interoperability with Kotlin.
@mk868, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template label.
If the issue is a question, add the I-question label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-* label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer label.
I can contribute to add these annotations.
Can I just create a Pull Request with changes?
Or Is additional analysis/confirmation needed for this feature by the Selenium team?
@mk868, yes, please. Focus on small PRs so they can be quickly reviewed and merged. It does not matter if you send many PRs. A PR with 2-3 files changed will be merged rather quickly, but a PR with 20 files changed will take several days.
Activity
github-actions commentedon Jul 22, 2024
@mk868, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
Triage this issue by using labels.
If information is missing, add a helpful comment and then
I-issue-templatelabel.If the issue is a question, add the
I-questionlabel.If the issue is valid but there is no time to troubleshoot it, consider adding the
help wantedlabel.If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable
G-*label, and it will provide the correct link and auto-close the issue.After troubleshooting the issue, please add the
R-awaiting answerlabel.Thank you!
github-actions commentedon Jul 25, 2024
This issue is looking for contributors.
Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.
mk868 commentedon Jul 26, 2024
I can contribute to add these annotations.
Can I just create a Pull Request with changes?
Or Is additional analysis/confirmation needed for this feature by the Selenium team?
diemol commentedon Jul 29, 2024
@mk868, yes, please. Focus on small PRs so they can be quickly reviewed and merged. It does not matter if you send many PRs. A PR with 2-3 files changed will be merged rather quickly, but a PR with 20 files changed will take several days.
[java] Add JSpecify annotations to WebElement and SearchContext (Seleβ¦
[java] Add JSpecify annotations to WebElement and SearchContext (Seleβ¦
[java] Add JSpecify annotations to WebElement and SearchContext (Seleβ¦
[java] Add JSpecify annotations to WebElement and SearchContext (#14319)
github-actions commentedon May 5, 2025
This issue is stale because it has been open 280 days with no activity. Remove stale label or comment or this will be closed in 14 days.
mk868 commentedon May 5, 2025
The task is still valid
66 remaining items
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
specify nullability in package `org.openqa.selenium.remote`
[java] specify nullability in package `org.openqa.selenium.remote` (#β¦
asolntsev commentedon Apr 14, 2026
In the end, this request was gradually implemented by many people in many pull requests:
https://github.com/SeleniumHQ/selenium/pulls?q=is%3Apr+is%3Aclosed+%2314291+
Big thanks to
github-actions commentedon May 14, 2026
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.