Summary: | Do not use undefined default param in CSSStyleDeclaration.idl | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Rob Buis <rbuis> | ||||
Component: | DOM | Assignee: | Rob Buis <rbuis> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | cdumez, darin, esprehn+autocc, ews-watchlist, glenn, gyuyoung.kim, kondapallykalyan, macpherson, menard, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Rob Buis
2020-08-22 10:12:48 PDT
Created attachment 407054 [details]
Patch
Comment on attachment 407054 [details]
Patch
Could we have added a tests? Or is there no way to detect that we are failing to look up "undefined" vs. failing to look up a null string?
(In reply to Darin Adler from comment #2) > Comment on attachment 407054 [details] > Patch > > Could we have added a tests? Or is there no way to detect that we are > failing to look up "undefined" vs. failing to look up a null string? I think the only way is through timing both lookups, and asserting that the null string lookup (early exit) will take less time than looking up "undefined". I personally thing this is a bit overkill but let me know if you want me to add such a test. Committed r266046: <https://trac.webkit.org/changeset/266046> All reviewed patches have been landed. Closing bug and clearing flags on attachment 407054 [details]. |