-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathstyle.css
More file actions
69 lines (64 loc) · 2.1 KB
/
Copy pathstyle.css
File metadata and controls
69 lines (64 loc) · 2.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
@import "tailwindcss";
@theme {
--color-brand-50: #f0fdfa;
--color-brand-100: #ccfbf1;
--color-brand-200: #99f6e4;
--color-brand-300: #5eead4;
--color-brand-400: #2dd4bf;
--color-brand-500: #14b8a6;
--color-brand-600: #0d9488;
--color-brand-700: #0f766e;
--color-brand-800: #115e59;
--color-brand-900: #134e4a;
--color-brand-950: #042f2e;
}
/*
The default border color has changed to `currentcolor` in Tailwind CSS v4,
so we've added these compatibility styles to make sure everything still
looks the same as it did with Tailwind CSS v3.
If we ever want to remove these styles, we need to add an explicit border
color utility to any element that depends on these defaults.
*/
@layer base {
*,
::after,
::before,
::backdrop,
::file-selector-button {
border-color: var(--color-gray-200, currentcolor);
}
}
/*
* Design-system foundation (UI-CORE). Before this layer existed the app never
* declared its own background, text color, or color-scheme, so the webview fell
* back to the OS-dark native defaults - which made dropdowns and text unreadable
* on a dark-theme OS. Declaring all three here is the single most important
* contrast fix: the app now owns its light/dark surfaces and tells the browser
* how to render native controls (selects, checkboxes, scrollbars). Teal is the
* app accent, so native checkboxes/radios get the teal accent-color too.
*/
@layer base {
:root {
color-scheme: light dark;
}
html,
body,
#app {
@apply bg-zinc-50 text-zinc-900 dark:bg-zinc-950 dark:text-zinc-100;
}
input[type="checkbox"],
input[type="radio"] {
@apply accent-teal-600;
}
/*
* Tailwind v3+ dropped the old preflight `cursor: pointer` reset for
* buttons, so every <button> in the app (every button/link-button, tab
* header, and icon button here is a native <button>) fell back to the
* browser's default arrow cursor on hover. One global rule fixes all of
* them; :not(:disabled) keeps disabled buttons on their existing
* `disabled:cursor-not-allowed` utility instead of fighting it.
*/
button:not(:disabled) {
cursor: pointer;
}
}