Summary: | Fix isCSSWideKeyword to stop including `default` | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Tim Nguyen (:ntim) <ntim> | ||||||
Component: | CSS | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED DUPLICATE | ||||||||
Severity: | Normal | CC: | darin, esprehn+autocc, ews-watchlist, glenn, gyuyoung.kim, macpherson, menard, webkit-bug-importer | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | WebKit Nightly Build | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Attachments: |
|
Description
Tim Nguyen (:ntim)
2021-04-20 08:41:55 PDT
Created attachment 426551 [details]
Patch
Created attachment 426552 [details]
Patch
I think it’s important to talk about the observable change we want in behavior rather than the internal function name. Do we have a test for the case where we end up handling "default" incorrectly? I still fully expect this will end up being a useful change once we understand why the tests we already have start indicating a failure and take care of that. We may need a different internal function to use where we are currently using isCSSWideKeyword. *** This bug has been marked as a duplicate of bug 232750 *** |