devs Tools / Paste Lab 0.4.0

CSS Doctor: Diagnose and repair HTML/CSS

Analyze HTML and CSS entirely in your browser, then diagnose cascade conflicts, overflow, sticky positioning, z-index, WordPress CSS, and more with evidence.

  • Pasted source stays in this browser
  • No source in URL, storage, or analytics
  • No arbitrary URL or JavaScript execution
21 active rules HTML · CSS · WordPress 日本語

Opening the isolated diagnostic workspace…

Workflow

From “CSS does not work” to evidence

  1. 01

    Paste a minimal reproduction

    Paste only the HTML and CSS required to reproduce the problem.

  2. 02

    Compare source and render

    A CSS AST checks structure while an isolated iframe measures layout, cascade, and focus.

  3. 03

    Preview the smallest safe change

    Review evidence, side effects, and before/after diff. Tier C guidance is never auto-applied.

Coverage

Problems CSS Doctor can investigate

Cascade and selectors

Specificity conflicts, duplicate declarations, broad selectors, and WordPress theme collisions.

Layout and responsive behavior

Horizontal overflow, fixed widths, flex minimum size, media size, sticky, stacking, and viewport units.

Accessibility and motion

Duplicate IDs, keyboard focus indicators, and reduced-motion alternatives.

Outside its scope

It does not fetch live sites, execute pasted JavaScript, or prove that code is bug-free.

Transparent rules

All 21 active rules are documented

Open the full rule reference

Glossary

Terms used in the report

Cascade(カスケード)
The CSS rule system that decides which declaration wins.
Specificity(詳細度)
A selector weight used in cascade decisions.
Runtime probe(表示実測)
A measurement taken after the sanitized code is rendered.
Safety Tier(修正安全度)
A is narrow and reversible, B needs review, and C is guidance only.
Confidence(確度)
How directly the available evidence supports a finding.
Stacking context(重なりのまとまり)
A local layering context that can trap a child z-index.

FAQ

Before using CSS Doctor

Is pasted code sent to the server?

No. Analysis, rendering, patching, and ZIP creation happen in this browser. Source is excluded from analytics and JSON reports.

Can it diagnose a live URL?

No. Arbitrary URL fetching is intentionally unsupported. Paste a minimal HTML/CSS reproduction instead.

Does “no findings” mean the code is correct?

No. It only means no issue supported by the current rules was detected under the selected conditions.

Can I paste the WordPress output directly?

Review the class scope and before/after result first. The block class field uses a name without a leading dot.