8 Commits

Include renames

Author	SHA1	Message	Date
ClintchizandClaude Opus 5	3441b96362	fix(csr): deliver focus and blur outputs from inside a component ... A parent writing @focus on a component tag never heard that component's own input or button take focus. The runtime bound every output-named DOM fallback listener in the bubble phase, and focus and blur do not bubble, so the event fired on the descendant and stopped there. Nothing errored -- the binding simply did nothing. That made a whole class of declared outputs undeliverable: button.focus, button.blur, TextLink.focus, TextLink.blur, WysiwygEditor.focus and WysiwygEditor.blur all advertised events they could never send. The ui ratchet for outputs nothing emits excluded natively-named outputs on the grounds that a native event reaches the root anyway. That holds for click and change, which bubble, and was wrong for focus and blur. Binding those two in the capture phase makes the exclusion honest rather than convenient; the ratchet's comment now says so. Also documents WysiwygEditor as the chrome shell it is: it emits none of its four outputs itself, it forwards whatever the slotted control raises. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-21 16:31:33 +05:30
Clintchiz	2c960fc1dc	refactor: migrate legacy wire namespace to wrn	2026-08-12 18:51:15 +05:30
Clintchiz	8d044565e3	feat: publish changed packages independently	2026-08-11 15:32:36 +05:30
Clintchiz	8f19a5eb2b	complete UI CSS ownership remediation	2026-08-09 21:42:30 +05:30
Clintchiz	324928cfca	refactor(ui): finish style-only component migration	2026-08-09 14:01:01 +05:30
Clintchiz	687d345882	release: WRNexusJS 0.6.0	2026-08-01 01:09:58 +05:30
Clintchiz	6afe32f63f	release: WRNexusJS 0.5.0	2026-07-29 12:51:10 +05:30
Clintchiz	c81dedff17	release: WRNexusJS 0.3.5	2026-07-24 12:46:44 +05:30