Personally I’m pretty frustrated with the way it works. I’ve noticed all of the following , and at least some of these apply to dev tools too. I don’t like the way Google controls the internet with Chrome, but at least its dev tools just work.

  • Sometimes when I try to use the element picker tool it actually clicks the element instead of selecting it in the toolbox
  • I can’t change selectors in CSS files in the sidebar, I have to go the style editor (Chrome lets me do this)
  • I can’t easily copy HTML attributes, if I double click on an attribute, the text is selected but when I press CMD C, it copies the entire tag with all of its attributes.
  • A lot of the time CSS properties I write just don’t apply and isn’t crossed out. Its like it just has a hard time doing that.
  • lettruthout@lemmy.worldEnglish
    1·
    10 months ago

    I’ve been using the Inspector and Console features for years and haven’t found that these things bother me, but all I’ve known is Firefox’s devtools. Recently took another look at the Debugger and found it to be very useful for React development. That, combined with the redux devtools extension, is very powerful.

  • Neshura@bookwormstory.socialEnglish
    1·
    10 months ago

    Honestly for me it’s the entire opposite, whenever I try to use Google’s dev tools I want to just quit. A lot of what you are describing seems like a bug to me though, especially since I don’t recall having most of these problems.

    Can’t speak on css properties not applying though as I usually edit those in a source file directly, either of the app I’m working with or the Stylus editor. The few cases where I do apply CSS through the dev tools do work though as long as they are modified in the correct place (occasionally tags nested deeper will override settings in non-obvious ways which might cause the observed effect)