Bug 314687
| Summary: | Web Inspector: `TestHarness.expect(Not)Null` should account for `undefined` | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Qianlang Chen <qianlangchen> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Qianlang Chen
Including `undefined` in these checks should make practical sense for JavaScript — callers typically care about "null-ish" rather than strictly `=== null`; relying on the latter in layout tests may introduce uncovered bugs due to the value being `undefined` unexpectedly
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
EWS
Committed 313273@main (e01a74ffaab3): <https://commits.webkit.org/313273@main>
Reviewed commits have been landed. Closing PR #64711 and removing active labels.
Radar WebKit Bug Importer
<rdar://problem/177111378>