Currently it is non-obvious how to get wd.w3cCompatible to be false.
This happens magically during capabilities parsing.
This change adds an explicit setter to toggle wd.w3cCompatible.
This config is needed because not all remotes behave nicely.
Being able to manually set wd.w3cCompatible to false is an escape hatch for issues with remotes.
Currently it is non-obvious how to get
wd.w3cCompatible
to befalse
. This happens magically during capabilities parsing.This change adds an explicit setter to toggle
wd.w3cCompatible
.This config is needed because not all remotes behave nicely. Being able to manually set
wd.w3cCompatible
tofalse
is an escape hatch for issues with remotes.