There are several issues introduced in r266885, most of them related to JSValue::get methods now returning an optional. In some cases of boolean values, the optional is checked instead of the contained bool or the logic is inverted. JSONValue::getString() is problematic too because it doesn't use optional, when you call getString() and null is returned it could be because the property is not present in the object or because the property is not a string. In several cases we need to know that so we need to first get the value and then call asString(9 instead of calling getString() directly.
Created attachment 408702 [details] Patch
Comment on attachment 408702 [details] Patch r=me, wow I can't believe I missed some of these subtleties 😳 thanks for fixing! Is there no EWS for WebDriver or anything? I wouldn't have landed the change if I'd known that things were broken 😞
Committed r267078: <https://trac.webkit.org/changeset/267078>
<rdar://problem/68903288>
(In reply to Devin Rousso from comment #2) > Comment on attachment 408702 [details] > Patch > > r=me, wow I can't believe I missed some of these subtleties 😳 thanks for > fixing! > > Is there no EWS for WebDriver or anything? I wouldn't have landed the > change if I'd known that things were broken 😞 No, we don't have EWS for WebDriver, the bots detected the issue.