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]: [dotnet] Statically generate atoms as native string instead of resources #16600
Here we see that each time when user writes element.IsDisplayed, then underhood selenium determines executing assembly's name and reads the content from assembly resources. It is not optimal.
The resources are static, there is no need to read it again and again.
Solution
Generate some *.cs file as compilation unit.
internalstaticclassMyResources{publicstaticconststringIsDisplayedResource="<this is generated during build stage>";}
Why
Performance;
Recently bazel changed resource names, so be less dependent on its behavior.
Have you considered any alternatives or workarounds?
Activity
selenium-ci commentedon Nov 15, 2025
@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.
Selenium Triage Team: remember to follow the Triage Guide
nvborisenko commentedon Nov 15, 2025
Before doing it let's manually verify whether we face escaping issues (when we past files content as literals in C#).
github-actions commentedon Dec 18, 2025
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.