RESOLVED FIXED 200240
Web Inspector: add -webkit-* keywords for *-height CSS properties
https://bugs.webkit.org/show_bug.cgi?id=200240
Summary Web Inspector: add -webkit-* keywords for *-height CSS properties
Devin Rousso
Reported 2019-07-29 14:02:21 PDT
intrinsic min-intrinsic min-content (and -webkit-min-content) max-content (and -webkit-max-content) -webkit-fill-available fit-content (and -webkit-fit-content) auto none (for max-* only)
Attachments
Patch (8.44 KB, patch)
2019-07-29 14:12 PDT, Devin Rousso
no flags
Devin Rousso
Comment 1 2019-07-29 14:12:55 PDT
Joseph Pecoraro
Comment 2 2019-07-29 14:36:37 PDT
Comment on attachment 375101 [details] Patch r=me
Nikita Vasilyev
Comment 3 2019-07-29 14:37:51 PDT
I wonder how feasible it is to make a script to parse & extract keyword values from WebCore/css/CSSValueKeywords.in and store them in a JS/JSON file that can be used by Web Inspector.
Devin Rousso
Comment 4 2019-07-29 15:41:57 PDT
Comment on attachment 375101 [details] Patch (In reply to Nikita Vasilyev from comment #3) > I wonder how feasible it is to make a script to parse & extract keyword values from WebCore/css/CSSValueKeywords.in and store them in a JS/JSON file that can be used by Web Inspector. CSSValueKeywords.in doesn't have a full mapping of CSS keyword to CSS property. The same is true of CSSProperties.json. Ideally, we'd merge the two files and have each property in CSSProperties.json have a list of all the keywords it accepts (which can then be used in place of CSSValueKeywords.in). In this case, the keywords aren't actually related to any CSS property in either file. They're checked during style conversion (StyleBuilderConverter.h).
WebKit Commit Bot
Comment 5 2019-07-29 16:06:32 PDT
Comment on attachment 375101 [details] Patch Clearing flags on attachment: 375101 Committed r247928: <https://trac.webkit.org/changeset/247928>
WebKit Commit Bot
Comment 6 2019-07-29 16:06:34 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 7 2019-07-29 16:07:17 PDT
Note You need to log in before you can comment on or make changes to this bug.