Description
Continuation of #16592
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.
internal static class MyResources
{
public static const string IsDisplayedResource = "<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?
No response