The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
How to debug @starting-style at-rule in Chrome DevTools
Chrome DevTools 143+ introduces a "starting-style" label in the Elements Panel for debugging the @starting-style at-rule. Clicking the label triggers transitions and displays the rule in the Styles pane for easy editing and debugging. Toggling the label again applies DevTools changes to the transition.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Brand guidelines fail when someone tries to use them. The PDF is complete. But when a developer needs something the system didn't anticipate, there's no logic to extend from. A style guide documents what exists. A system tells you what to do next.
Mind blowing job
Side Pocket, behind the site.
This is the Figma file for my Lovable Challenge entry:
Every page at five breakpoints, from 1920 down to 390
Components with default and hover states
One set of text and color styles for the whole site
Home, menu, booking and the staff screens all live in one file. Changes get planned in the design first, then go to code.
Live site: side-pocket.lovable.app
midcode is out. 🎉
The mid between code and no-code: open the site you built in code on a live canvas, click anything, change it by hand. Every edit lands in your files as a clean diff.
— Design and Code, side by side
— Your agent (Claude Code, Codex, Gemini) built in
— Branching
— Locale support (multi-language)
— A CMS for the content in your code [BETA]
3 day free trial
Lifetime payment of $119 for the first 50 (then $199).
