RESOLVED DUPLICATE of bug 190254 190246
Fix Pointer Event feature.json entry 
https://bugs.webkit.org/show_bug.cgi?id=190246
Summary Fix Pointer Event feature.json entry
Don Olmstead
Reported 2018-10-03 05:02:45 PDT
Currently the style checker fails on Pointer Event's features.json values.
Attachments
Patch (1.22 KB, patch)
2018-10-03 05:04 PDT, Don Olmstead 		no flags
DetailsFormatted DiffDiff
Patch (1.36 KB, patch)
2018-10-03 05:12 PDT, Don Olmstead 		no flags
DetailsFormatted DiffDiff
Patch (1.35 KB, patch)
2018-10-03 05:47 PDT, Don Olmstead 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Don Olmstead
Comment 1 2018-10-03 05:04:37 PDT
Created attachment 351509 [details] Patch
EWS Watchlist
Comment 2 2018-10-03 05:07:42 PDT
Attachment 351509 [details] did not pass style-queue: ERROR: Source/WebCore/features.json:0: The feature "Pointer Events" has a specification field but no specification of that name exists. [json/syntax] [5] Total errors found: 1 in 2 files If any of these errors are false positives, please file a bug against check-webkit-style.
Don Olmstead
Comment 3 2018-10-03 05:12:44 PDT
Created attachment 351510 [details] Patch
EWS Watchlist
Comment 4 2018-10-03 05:15:52 PDT
Attachment 351510 [details] did not pass style-queue: ERROR: Source/WebCore/features.json:0: The feature "Pointer Events" has a specification field but no specification of that name exists. [json/syntax] [5] Total errors found: 1 in 2 files If any of these errors are false positives, please file a bug against check-webkit-style.
Don Olmstead
Comment 5 2018-10-03 05:47:24 PDT
Created attachment 351514 [details] Patch
Don Olmstead
Comment 6 2018-10-03 05:51:39 PDT
Comment on attachment 351514 [details] Patch The features.json did not want the specification field in there.
Joseph Pecoraro
Comment 7 2018-10-04 11:24:57 PDT
Looks like this was fixed by: https://bugs.webkit.org/show_bug.cgi?id=190254 *** This bug has been marked as a duplicate of bug 190254 ***
Note You need to log in before you can comment on or make changes to this bug.