Kevin Powell

@jerrychen1013 I believe you'll need to add the following to your `ESLint-Formatter.sublime-settings - User` file (accessed by Sublime Text > Preferences > Package Settings > ESLintFormatter > Settings menu) ```...

I've tried a restart, but am experiencing the same issue. Nothing showing up in my Automation preferences pane.

I'm also seeing this issue. Not only does color not update in the Sketch document, it prevents the entire style block from functioning. Example: ``` [type="text"] { color: #ff0000; text-transform:...

I'm using chromy in backstopjs as well and can confirm that adding: ``` body { position: relative; } ``` To the page I was testing made these errors go away....

Solid integration with Storybook would be beneficial for the work I do. [Chromatic](https://www.chromatic.com) and [Percy](https://percy.io) do this really well. Also a UI for reviewing the diffs would be great.

I actually prefer the pixel highlighting (like Playwright already does), but organize all the failing tests in a UI so I can see what failed without having to poke around...

Slider is rarely useful for me. An onion-skin (transparency overlay) would be more useful.

I tend to refer to them as “source” files as well. “Token source file” or “design token source file” makes sense to me.

@runem what does agreement look like? Looks like it's already been discussed: https://github.com/webcomponents/custom-elements-json/issues/5#issuecomment-546843921 Is there an official doc that I'm not seeing?

@runem thanks for the response. I'd love to use that experimental format in the interim. I understand the blocker that is the standardization conversation.