REGRESSION (r236091): CSSKeywordCompletions.js has "checkout" instead of "check-out" as a value for -apple-pay-button-type
Created attachment 351122 [details] Patch
In reality, these completions only serve to provide autocompletion for older backends. It's still good to have it correct, but future releases won't need this list. :)
Comment on attachment 351122 [details] Patch Clearing flags on attachment: 351122 Committed r236622: <https://trac.webkit.org/changeset/236622>
All reviewed patches have been landed. Closing bug.
<rdar://problem/44878214>
Comment on attachment 351122 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=351122&action=review > Source/WebInspectorUI/ChangeLog:8 > + I changed "checkout" to "check-out" in r235754, but it somehow got flipped back to "checkout" in r236091. Is this testable?
(In reply to Alexey Proskuryakov from comment #6) > Comment on attachment 351122 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=351122&action=review > > > Source/WebInspectorUI/ChangeLog:8 > > + I changed "checkout" to "check-out" in r235754, but it somehow got flipped back to "checkout" in r236091. > > Is this testable? I'm guessing no, because it would require running the front-end against an older backend. Devin would know for sure.
Comment on attachment 351122 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=351122&action=review >>> Source/WebInspectorUI/ChangeLog:8 >>> + I changed "checkout" to "check-out" in r235754, but it somehow got flipped back to "checkout" in r236091. >> >> Is this testable? > > I'm guessing no, because it would require running the front-end against an older backend. Devin would know for sure. That is correct. We'd need to run the current WebInspector front-end against a pre-r236091 backend.