Tailwind compatibility scope

BaroCSS uses Tailwind-style class names. It does not claim full Tailwind CSS compatibility or a measured compatibility percentage.

Selected comparison evidence

An earlier candidate revision was compared with tailwindcss@4.1.13 using 15 selected classes. The comparison checks generated CSS structure. A structural difference alone does not prove a visual difference. This small sample cannot measure overall coverage.

That revision also has a Chromium browser comparison for hover:block, md:block, mask-linear-from-50%, and inset-ring-2 in specific states and with specific theme values. Those four inputs matched the checked computed styles or rendered pixels. Firefox, WebKit, other themes, other class combinations, and the full Tailwind feature set were not checked.

The fixture list and comparison method and independent candidate review give the test inputs and limits. These earlier candidate records do not establish full compatibility for the published 0.5.0 package. They are not a release support policy.

Before migrating

Test the classes and browsers your application uses. Compare the generated styles in real pages, including responsive states and theme overrides. If a class emits no rule or renders differently, keep your existing CSS for that case and report the input and observed result.