Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Certain API methods are not available

See original GitHub issue

When I try to use the CSS.toggleProperty method defined in the Chrome Debugger Protocol Viewer docs, I get an error:

>>> CSS.toggleProperty({ 'styleId': { 'styleSheetId': '56219.1', 'ordinal': 1 }, 'propertyIndex': 1, 'disable': true })
TypeError: CSS.toggleProperty is not a function
    at repl:1:5
    at REPLServer.defaultEval (repl.js:250:27)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:412:12)
    at emitOne (events.js:82:20)
    at REPLServer.emit (events.js:169:7)
    at REPLServer.Interface._onLine (readline.js:210:10)
    at REPLServer.Interface._line (readline.js:549:8)
    at REPLServer.Interface._ttyWrite (readline.js:826:14)

The same happens for DOM.setInspectModeEnabled.

>>> DOM.setInspectModeEnabled({ 'enabled': true })
TypeError: DOM.setInspectModeEnabled is not a function
    at repl:1:5
    at REPLServer.defaultEval (repl.js:250:27)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:412:12)
    at emitOne (events.js:82:20)
    at REPLServer.emit (events.js:169:7)
    at REPLServer.Interface._onLine (readline.js:210:10)
    at REPLServer.Interface._line (readline.js:549:8)
    at REPLServer.Interface._ttyWrite (readline.js:826:14)

Issue Analytics

State:
Created 7 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

1reaction

aslushnikovcommented, Oct 4, 2016

@sarahlim which range are you sending? The style range should start right after the rule’s { and end before rule’s ending }.

here’s the inspector-protocol test which exercises this method: link

1reaction

cyrus-andcommented, Oct 4, 2016

@sarahlim since I’m reading this anyway, here’s my two cents…

The fact is that figuring out the proper source range can be tricky and AFAIK there is no protocol method that aids you in figuring out the range given a CSS rule selector; you need to first walk the matched CSS rules for a given a NodeId with CSS.getMatchedStylesForNode. Which seems to be what DevTools does when you toggle the checkbox of a CSS rule (if you inspect its WebSocket).

I don’t know about your use case, but another approach would be: fetch the whole style sheet text with CSS.getStyleSheetText, perform the desired modifications and replace the original one with CSS.setStyleSheetText.