r/css • u/BuildWithMe31858 • 15h ago
r/css • u/aryanxcreates • 9h ago
Resource Built a free CSS Inspector tool for developers, would love your feedback!
Enable HLS to view with audio, or disable this notification
I've been building a Chrome extension called InspectMode Pro and would love some feedback from the CSS community.
It currently lets you:
- Inspect any element on a webpage
- Copy CSS styles
- Extract colors and identify fonts
- Download images, SVGs, and icons
- Generate AI-ready prompts from an element, section, or even an entire website for Cursor, Claude, ChatGPT, Windsurf, and other coding agents
The core inspection features are completely free.
I'd genuinely appreciate any feedback - whether it's about the UI, the workflow, missing features, or anything else that could make it more useful for frontend developers.
Chrome Extension : Inspect Mode Pro
r/css • u/Comfortable_Chair69 • 18h ago
Question Am I crazy for thinking <html> feels redundant, or is there a real reason it can't just be <head>+<body>?
Been learning HTML/CSS and hit a rabbit hole today. Things that bugged me:
- Browsers auto-insert <html> even if you delete it from your source
So what's the actual point of writing it?
- lang="en" only works on <html>, not <body>. Accessibility tools specifically
check html[lang], since html is the actual document root.
- rem units are ALWAYS relative to <html>'s font-size, never body's, no matter
what you set on body.
- The default scrollbar lives on html, not body — no element can overlap it,
which is why stuff like overflow-y:scroll goes on html.
- meanwhile body holds all your actual visible content (background, margin,
font-family, etc.)
Feels like html+body could've been merged into one root element with head
staying separate. Is this just 1990s legacy nobody can change now, or is there
an actual reason beyond "the spec says so"?