@lynx-js/web-core@0.23.0

Minor Changes

• Add a bidirectional per-card devtool event channel. Background scripts can use lynx.getDevtool() to dispatch events to a devtoolMessage event on <lynx-view> and listen for events sent through lynxView.sendDevtoolEvent(). (#2999)

Patch Changes

• fix auto-height for frame (#3062)

• Reuse the first bundle loaded for a URL and ignore override configs from later requests without replacing or disposing the cached bundle. (#3164)

• Fix nativeApp.callLepusMethod always invoking its callback with undefined: the UI-thread handler now returns the lepus method's result so the callback receives it. (#2994)

• Include the <lynx-view> host and page baseline styles in its shadow root so client rendering and declarative Shadow DOM SSR do not depend on the outer document stylesheet. (#3004)

• Map the Lynx textarea tag to the x-textarea custom element when creating elements on web. (#2971)

  __CreateElement looked up LYNX_TAG_TO_HTML_TAG_MAP, which had no textarea entry, so textarea fell through to a bare HTML <textarea> instead of the x-textarea custom element registered by @lynx-js/web-elements. Because the element was never x-textarea, none of the Lynx event forwarding (input/focus/blur) was wired up, so typed input never bridged to the framework thread — any bindinput/@input binding (e.g. Vue's v-model) silently did nothing. input already worked because it was mapped to x-input.

  Adding textarea: 'x-textarea' to the map makes textarea render as x-textarea, matching native Lynx and the existing input behavior; the runtime event tables already know how to bridge x-textarea's lynxinput/lynxfocus/lynxblur events. The same entry is added to the parallel Rust map (src/constants.rs) so textarea type selectors in Lynx stylesheets are rewritten to x-textarea and keep matching the rendered element.

• Updated dependencies [087a59b, 5a83170, 0d3623b, a1cccf9, 226ac0e, 02c875c]:

  • @lynx-js/web-elements@0.12.7
  • @lynx-js/css-serializer@0.1.7
  • @lynx-js/web-worker-rpc@0.23.0