@yuneta/gobj-ui 3.0.0 → 4.0.0

package/src/c_yui_shell.css

@@ -4,6 +4,31 @@
  *      Depends on Bulma being loaded (uses .tabs, .menu, .level, is-*, etc.)
  ***********************************************************************/
 
+/*============================================================
+ *      Native control scheme
+ *
+ *      The browser draws the ornaments of native controls itself —
+ *      number-input spinners, the select chevron, scrollbars, the
+ *      date picker — and picks their colours from `color-scheme`,
+ *      NOT from the background/color we set. Nobody declared it, so
+ *      they rendered light in a dark app whatever the CSS said.
+ *      Bulma flips its palette on [data-theme]; this makes the
+ *      browser's own chrome follow the same switch.
+ *============================================================*/
+/*  No [data-theme] is the "system" theme: Bulma renders per
+ *  prefers-color-scheme, so `light dark` — "supports both, follow the
+ *  OS" — is what tracks it. Pinning `light` here would force light
+ *  controls inside a system-dark app: the very bug this fixes. */
+:root {
+    color-scheme: light dark;
+}
+:root[data-theme="light"] {
+    color-scheme: light;
+}
+:root[data-theme="dark"] {
+    color-scheme: dark;
+}
+
 /*============================================================
  *      Root + layers
  *============================================================*/
@@ -590,6 +615,14 @@
     white-space: nowrap;
     font-weight: 600;
 }
+/*  Separator between the data half and the translated kind half. CSS,
+ *  not a text node: createElement2 trims text nodes and eats the spaces. */
+.MODAL_TITLE_PREFIX + .MODAL_TITLE_KIND::before {
+    content: "·";
+    padding: 0 0.4em;
+    color: var(--bulma-text-weak);
+    font-weight: 400;
+}
 .yui-dialog-back,
 .yui-dialog-x {
     flex: 0 0 auto;