Bug 113025

Summary: Web Inspector: Fix JSDocs.
Product: WebKit Reporter: Eugene Klyuchnikov <eustas>
Component: Web Inspector (Deprecated)Assignee: Eugene Klyuchnikov <eustas>
Status: RESOLVED FIXED    
Severity: Normal CC: apavlov, dglazkov, graouts, joepeck, keishi, loislo, pfeldman, pmuellr, timothy, vsevik, web-inspector-bugs, webkit.review.bot, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch
none
Patch
none
Archive of layout-test-results from gce-cr-linux-02 for chromium-linux-x86_64 none

Eugene Klyuchnikov
Reported 2013-03-22 02:09:35 PDT
Next version of JS compiler finds more inconsistencies and ambiguous declarations. Some of them are fixed in this patch.
Attachments
Patch (7.47 KB, patch)
2013-03-22 02:11 PDT, Eugene Klyuchnikov
no flags
Patch (6.83 KB, patch)
2013-03-25 00:56 PDT, Eugene Klyuchnikov
no flags
Archive of layout-test-results from gce-cr-linux-02 for chromium-linux-x86_64 (616.22 KB, application/zip)
2013-03-25 02:36 PDT, WebKit Review Bot
no flags
Eugene Klyuchnikov
Comment 1 2013-03-22 02:11:37 PDT
Eugene Klyuchnikov
Comment 2 2013-03-25 00:56:51 PDT
WebKit Review Bot
Comment 3 2013-03-25 02:36:54 PDT
Comment on attachment 194796 [details] Patch Attachment 194796 [details] did not pass chromium-ews (chromium-xvfb): Output: http://webkit-commit-queue.appspot.com/results/17242412 New failing tests: fast/css/font-family-pictograph.html
WebKit Review Bot
Comment 4 2013-03-25 02:36:57 PDT
Created attachment 194807 [details] Archive of layout-test-results from gce-cr-linux-02 for chromium-linux-x86_64 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: gce-cr-linux-02 Port: chromium-linux-x86_64 Platform: Linux-3.3.8-gcg-201212281604-x86_64-with-GCEL-10.04-gcel_10.04
Eugene Klyuchnikov
Comment 5 2013-03-25 04:37:39 PDT
Comment on attachment 194796 [details] Patch Clearing flags on attachment: 194796 Committed r146757: <http://trac.webkit.org/changeset/146757>
Note You need to log in before you can comment on or make changes to this bug.