RibbonWeb Blazor 0.2.2

RibbonWeb.Blazor 0.2.2

Adopts shared runtime c833be49d472583b6f56225862e0aa7d201c1da7, validated and merged through Dockyard PR #5. Fixes concurrent visual disposal, late Razor module imports and root creation, queued callbacks after removal, and repeated cleanup failures. Adds lifecycle state, awaitable factory teardown and coalesced template updates.

Preserves RibbonControl, typed definitions, real Razor custom controls and the compatible RibbonWeb/ICommand APIs and asset paths. The canonical project remains dotnet/RibbonWeb.Blazor.csproj. Both READMEs identify the new version.

.NET 8/.NET 10 actual-package WebAssembly/Interactive Server tests include template movement/update/recreation, managed disposal races, native interactions and compatible event forwarding. Eight new shared JavaScript lifecycle cases accompany existing checks. Publication validates public NuGet bytes before creating packages, symbols and runnable-sample releases. Native callback and engine compatibility boundaries remain unchanged.

RibbonWeb Blazor 0.2.1

RibbonWeb.Blazor 0.2.1

Updates the pinned interop runtime to the tested Dockyard revision 1c895b7184451071e1c7131063249d2d9eb145b9, with no Dockyard runtime dependency.

• Preserve cyclic/deep native argument graphs and shared callback identity without mutating inputs.
• Await concurrent native/module/subscription cleanup and asynchronous unsubscribe, continuing teardown after individual failures.
• Preserve property, method and disposal access through callable handles.
• Honor initialization-wait cancellation independently for each caller; prevent late native construction after disposal.
• Add complete streamed callable results through CallFunctionJsonAsync<T> and expanded JavaScript/managed regressions.

The compatible RibbonWeb component, RibbonWebInterop, ICommand integration, typed RibbonControl, real Razor custom controls and original static asset paths are preserved. Both .NET 8/.NET 10 WebAssembly and Interactive Server package consumers must pass validation before publication. Public NuGet payloads are verified before release creation.

RibbonWeb Blazor 0.2.0

RibbonWeb.Blazor 0.2.0

• Extend the canonical package to .NET 8/.NET 10 while preserving the existing RibbonWeb component, ICommand and original asset paths.
• Add typed definitions, native RibbonControl, Razor custom render factories and native function handles.
• Correct Server sample namespace resolution; qualify native Razor callbacks and compatible .NET event forwarding.
• Add streamed data/binary interop, explicit literal payloads, async lifecycle cleanup and scoped template roots.
• Package-restored WebAssembly/Server samples, root documentation, independent NuGet publication and public-payload verification.
• Update the Node browser-test runner from vulnerable Playwright 1.55.0 to the locked 1.63.0 version used by sibling projects.

Native compatibility boundaries remain applicable. Typed convenience APIs are complemented by generic native interop; synchronous native callbacks execute in the browser. Independent Razor roots do not automatically inherit outer cascading values.

RibbonWeb v0.1.1

Changelog

0.1.1 — 2026-09-12

• Publish the existing @wieslawsoltes/ribbon-web package to npm with provenance after release validation.
• Verify SHA-256 release checksums, immutable SHA-512 npm integrity, distribution tags, public package indexing and provenance, and fresh anonymous package installation.
• Test the actual installed tarball: public ESM subpaths, shared core class identity, MVVM bindings and commands, strict TypeScript declarations, and browser Shadow DOM styles and interactions.
• Preserve existing release attachments during retries; separate reusable npm recovery from archive creation.
• Add CI, release/npm, version, downloads, license and demo badges and simplify installation instructions.
• Align the Blazor package and release manifest at 0.1.1.

0.1.0 — 2026-09-11

Initial public release of RibbonWeb, a standalone native-ESM ribbon component for browser applications and .NET application ports.

Component and integration

• Reusable custom element with a model-driven API and .NET-style patterns for commands, observables and MVVM bindings.
• Ribbon controls, contextual surfaces and application showcase examples are documented in the README and capability matrix.
• Separate core, ribbonx and dotnet entry points allow applications to import the relevant layer.
• TypeScript declarations ship with the JavaScript package.
• A buildable .NET 8 Razor class library packages the component and all browser assets for Blazor.
• 34 Node tests, 58 Chromium behavior groups (including 29 RibbonX assertions), and strict TypeScript usage checks pass.

Distribution

• MIT license and zero runtime package dependencies.
• Native ESM output can be hosted directly, consumed through npm, or served by a package CDN after registry publication.
• Reproducible build scripts produce an npm tarball, a browser distribution ZIP, a complete source ZIP and SHA-256 checksums.
• CI checks JavaScript syntax, model behavior, browser interaction and packaging.
• GitHub Pages workflow publishes the interactive showcase, documentation and downloadable distributions.
• Version-tag, release-manifest or manual release workflow publishes GitHub release artifacts. npm publishing is enabled when the maintainer provides NPM_TOKEN; GitHub Packages publishing is enabled with the repository variable PUBLISH_GITHUB_PACKAGES=true. NuGet.org publishing is enabled with NUGET_API_KEY.

Compatibility notes

This release is an independent browser ribbon implementation. The capability matrix records supported controls, platform adaptations and remaining gaps. Application command implementations, document formats and the complete proprietary APIs of desktop productivity suites are outside the ribbon control's contract. Registry pipeline support does not itself mean a package has already been published to that registry.

RibbonWeb v0.1.0

Changelog

0.1.0 — 2026-09-11

Initial public release of RibbonWeb, a standalone native-ESM ribbon component for browser applications and .NET application ports.

Component and integration

• Reusable custom element with a model-driven API and .NET-style patterns for commands, observables and MVVM bindings.
• Ribbon controls, contextual surfaces and application showcase examples are documented in the README and capability matrix.
• Separate core, ribbonx and dotnet entry points allow applications to import the relevant layer.
• TypeScript declarations ship with the JavaScript package.
• A buildable .NET 8 Razor class library packages the component and all browser assets for Blazor.
• 34 Node tests, 58 Chromium behavior groups (including 29 RibbonX assertions), and strict TypeScript usage checks pass.

Distribution

• MIT license and zero runtime package dependencies.
• Native ESM output can be hosted directly, consumed through npm, or served by a package CDN after registry publication.
• Reproducible build scripts produce an npm tarball, a browser distribution ZIP, a complete source ZIP and SHA-256 checksums.
• CI checks JavaScript syntax, model behavior, browser interaction and packaging.
• GitHub Pages workflow publishes the interactive showcase, documentation and downloadable distributions.
• Version-tag, release-manifest or manual release workflow publishes GitHub release artifacts. npm publishing is enabled when the maintainer provides NPM_TOKEN; GitHub Packages publishing is enabled with the repository variable PUBLISH_GITHUB_PACKAGES=true. NuGet.org publishing is enabled with NUGET_API_KEY.

Compatibility notes

This release is an independent browser ribbon implementation. The capability matrix records supported controls, platform adaptations and remaining gaps. Application command implementations, document formats and the complete proprietary APIs of desktop productivity suites are outside the ribbon control's contract. Registry pipeline support does not itself mean a package has already been published to that registry.