Bug 113176 – Web Inspector: Graduate some new Inspector APIs to public

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Vladislav Kaznacheev]

There is a number of APIs that are stable enough to be fixed.
Below is the output of the updated API validator(see https://bugs.webkit.org/show_bug.cgi?id=113148) listing the proposed changes:

    DOM.highlightNode.nodeId: required parameter is now optional
    Input: domain has been added
    Runtime.enable: command has been added
    Runtime.executionContextCreated: event has been added
    Page.clearGeolocationOverride: command has been added
    Page.setGeolocationOverride: command has been added
    Page.captureScreenshot: command has been added
    Debugger.setBreakpointByUrl.locations: optional response parameter is now required

[Vladislav Kaznacheev]

Created attachment 194802 [details]
Patch

[Timothy Hatcher]

Nice first step. But lets go further. Surely more things are stable than that measly list!

My proposed list:

Page.Frame
Page.FrameResourceTree
Page.getResourceTree
Page.getResourceContent
Page.searchInResource
Page.searchInResources
Page.frame* (events)

Network.FrameId

*.frameId (parameters)

DOM.performSearch
DOM.getSearchResults
DOM.discardSearchResults

CSS.* (except named flow stuff)

[WebKit Review Bot]

Comment on attachment 194802 [details]
Patch

Clearing flags on attachment: 194802

Committed r146777: <http://trac.webkit.org/changeset/146777>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.

[Pavel Feldman]

(In reply to comment #2)
> Nice first step. But lets go further. Surely more things are stable than that measly list!
> 
> My proposed list:
> 
> Page.Frame
> Page.FrameResourceTree
> Page.getResourceTree
> Page.getResourceContent
> Page.searchInResource
> Page.searchInResources
> Page.frame* (events)
> 
> Network.FrameId
> 
> *.frameId (parameters)
> 

The ones above look good to me, they all match our plans.

> DOM.performSearch
> DOM.getSearchResults
> DOM.discardSearchResults

I don't see why not.

> 
> CSS.* (except named flow stuff)

CSS domain requires some heavy lifting, so I'd leave it for longer term...

[Timothy Hatcher]

(In reply to comment #5)
> (In reply to comment #2)
> > CSS.* (except named flow stuff)
> 
> CSS domain requires some heavy lifting, so I'd leave it for longer term...

Where are the bugs tracking planned incompatible work? If there are none, then this domain is stable IMHO.