Andreas Reinhold / reiniandClaude Opus 5
50431181a7
A rewritten component's padding, margin and border sit in material.components, which the Workbench declared below all of Tailwind's layers, so preflight's universal reset beat them. The entry's layer statement now puts material between base and components (plan step 36): the material reset already carries preflight, and every utility still outranks the package. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
17 lines
960 B
CSS
17 lines
960 B
CSS
/* The Workbench builds the package as an application would, with explicit sources so the plans
|
|
in docs/ are not scanned for class names. The layer statement puts the `material` layers above
|
|
Tailwind's preflight (`base`) and below its `components` and `utilities`: a rewritten component's
|
|
padding, margin and border would otherwise lose to preflight's `* { padding: 0 }`, which the
|
|
material reset already carries, while every utility still outranks the package. tailwind.css
|
|
brings the components still written for Tailwind, without declaring the tokens a second time. */
|
|
@layer theme, base, material, components, utilities;
|
|
@import '../../../resources/css/foundation.css';
|
|
@import '../../../resources/css/layout.css';
|
|
@import '../../../resources/css/components.css';
|
|
@import 'tailwindcss' source(none);
|
|
@import '../../../resources/css/tailwind.css';
|
|
@import './material-scheme.css';
|
|
|
|
@source '../../../resources/views';
|
|
@source '../../../src';
|