Summary: | new-run-webkit-websocketserver doesn't work after Chromium removal | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> | ||||
Component: | New Bugs | Assignee: | Ryosuke Niwa <rniwa> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, benjamin, dpranke, jberlin, joepeck | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Ryosuke Niwa
2013-05-08 12:10:44 PDT
Created attachment 201092 [details]
Fixes the bug
Comment on attachment 201092 [details] Fixes the bug View in context: https://bugs.webkit.org/attachment.cgi?id=201092&action=review Looks good to me! Thanks. > Tools/Scripts/new-run-webkit-websocketserver:38 > +from webkitpy.port import platform_options Alphabetical order? Or does that style not matter in py. > Tools/Scripts/new-run-webkit-websocketserver:106 > # FIXME: Make this work with other ports as well. Seems like you can remove the FIXME now. Committed r149757: <http://trac.webkit.org/changeset/149757> |