@floegence/floe-webapp-init 0.50.4 → 0.50.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@floegence/floe-webapp-init",
3
- "version": "0.50.4",
3
+ "version": "0.50.6",
4
4
  "license": "MIT",
5
5
  "type": "module",
6
6
  "description": "Scaffolding tool for Floe Webapp applications",
@@ -47,6 +47,7 @@ description: Implement, refactor, and debug Floe-Webapp apps and this monorepo u
47
47
  - `@floegence/floe-webapp-core/workbench`
48
48
  - `@floegence/floe-webapp-core/styles`
49
49
  - `@floegence/floe-webapp-core/tailwind`
50
+ - `@floegence/floe-webapp-core/input-focus.css` (standalone input borders without shell styles)
50
51
  4. Align registry behavior end-to-end:
51
52
  - Keep `FloeComponent.id`, sidebar items, command targets, and layout navigation consistent.
52
53
  - Use `ActivityAppsMain` for `sidebar.fullScreen` or `sidebar.renderIn === 'main'` page flows when appropriate.
@@ -82,6 +82,7 @@ done
82
82
  - `@floegence/floe-webapp-core/full`
83
83
  - `@floegence/floe-webapp-core/styles`
84
84
  - `@floegence/floe-webapp-core/tailwind`
85
+ - `@floegence/floe-webapp-core/input-focus.css`
85
86
  3. Do not import `@floegence/floe-webapp-core/src/...`.
86
87
  4. Prefer `@floegence/floe-webapp-core/tailwind` for Tailwind v4 apps; use `@floegence/floe-webapp-core/styles` only as the no-Tailwind fallback.
87
88
 
@@ -142,3 +143,7 @@ pnpm verify
142
143
  - Fix the nearest root cause.
143
144
  - Re-run from the failed command onward.
144
145
  - Do a final review of the changed files for consistency and completeness before committing.
146
+
147
+ ## Input focus boundaries
148
+
149
+ Text inputs, textareas, and native selects change only their existing border color on focus. Mark a composite control's visible boundary with `data-floe-input-surface` and leave its inner editor frameless. Keep independent buttons and navigation keyboard-visible. Standalone host-owned documents can load `@floegence/floe-webapp-core/input-focus.css` and map `--ring`, `--error`, `--accent`, and `--accent-foreground` to their theme. The asset has no shell imports; do not copy it or inject it into third-party frames.
@@ -47,6 +47,7 @@ description: Implement, refactor, and debug Floe-Webapp apps and this monorepo u
47
47
  - `@floegence/floe-webapp-core/workbench`
48
48
  - `@floegence/floe-webapp-core/styles`
49
49
  - `@floegence/floe-webapp-core/tailwind`
50
+ - `@floegence/floe-webapp-core/input-focus.css` (standalone input borders without shell styles)
50
51
  4. Align registry behavior end-to-end:
51
52
  - Keep `FloeComponent.id`, sidebar items, command targets, and layout navigation consistent.
52
53
  - Use `ActivityAppsMain` for `sidebar.fullScreen` or `sidebar.renderIn === 'main'` page flows when appropriate.
@@ -82,6 +82,7 @@ done
82
82
  - `@floegence/floe-webapp-core/full`
83
83
  - `@floegence/floe-webapp-core/styles`
84
84
  - `@floegence/floe-webapp-core/tailwind`
85
+ - `@floegence/floe-webapp-core/input-focus.css`
85
86
  3. Do not import `@floegence/floe-webapp-core/src/...`.
86
87
  4. Prefer `@floegence/floe-webapp-core/tailwind` for Tailwind v4 apps; use `@floegence/floe-webapp-core/styles` only as the no-Tailwind fallback.
87
88
 
@@ -142,3 +143,7 @@ pnpm verify
142
143
  - Fix the nearest root cause.
143
144
  - Re-run from the failed command onward.
144
145
  - Do a final review of the changed files for consistency and completeness before committing.
146
+
147
+ ## Input focus boundaries
148
+
149
+ Text inputs, textareas, and native selects change only their existing border color on focus. Mark a composite control's visible boundary with `data-floe-input-surface` and leave its inner editor frameless. Keep independent buttons and navigation keyboard-visible. Standalone host-owned documents can load `@floegence/floe-webapp-core/input-focus.css` and map `--ring`, `--error`, `--accent`, and `--accent-foreground` to their theme. The asset has no shell imports; do not copy it or inject it into third-party frames.
@@ -47,6 +47,7 @@ description: Implement, refactor, and debug Floe-Webapp apps and this monorepo u
47
47
  - `@floegence/floe-webapp-core/workbench`
48
48
  - `@floegence/floe-webapp-core/styles`
49
49
  - `@floegence/floe-webapp-core/tailwind`
50
+ - `@floegence/floe-webapp-core/input-focus.css` (standalone input borders without shell styles)
50
51
  4. Align registry behavior end-to-end:
51
52
  - Keep `FloeComponent.id`, sidebar items, command targets, and layout navigation consistent.
52
53
  - Use `ActivityAppsMain` for `sidebar.fullScreen` or `sidebar.renderIn === 'main'` page flows when appropriate.
@@ -82,6 +82,7 @@ done
82
82
  - `@floegence/floe-webapp-core/full`
83
83
  - `@floegence/floe-webapp-core/styles`
84
84
  - `@floegence/floe-webapp-core/tailwind`
85
+ - `@floegence/floe-webapp-core/input-focus.css`
85
86
  3. Do not import `@floegence/floe-webapp-core/src/...`.
86
87
  4. Prefer `@floegence/floe-webapp-core/tailwind` for Tailwind v4 apps; use `@floegence/floe-webapp-core/styles` only as the no-Tailwind fallback.
87
88
 
@@ -142,3 +143,7 @@ pnpm verify
142
143
  - Fix the nearest root cause.
143
144
  - Re-run from the failed command onward.
144
145
  - Do a final review of the changed files for consistency and completeness before committing.
146
+
147
+ ## Input focus boundaries
148
+
149
+ Text inputs, textareas, and native selects change only their existing border color on focus. Mark a composite control's visible boundary with `data-floe-input-surface` and leave its inner editor frameless. Keep independent buttons and navigation keyboard-visible. Standalone host-owned documents can load `@floegence/floe-webapp-core/input-focus.css` and map `--ring`, `--error`, `--accent`, and `--accent-foreground` to their theme. The asset has no shell imports; do not copy it or inject it into third-party frames.