Fluentqt

collection input signals, FlowView layout reentry, and NumberBox callback
lifetime handling. It also updates the development guides and project website.

ToggleSwitch sizing

`ToggleSwitch::visualScale` scales the track, knob, and content gap without
changing the text font or an explicitly fixed widget size. The default is

[Contents](../SUMMARY.md) · [Releases index](README.md)
<!-- docs-nav:top:end -->

C++ library, PySide6 bindings, desktop Galleries, and WebAssembly delivery. It
also gives focused multi-line text input a smoother, policy-aware auto-height
transition while keeping programmatic sizing synchronous.

Accessible appearance and motion

- Applications can select a complete `HighContrast` semantic palette without
replacing the Fluent design contract. Existing Light and Dark palettes keep
their previous values, and apps that do not opt in retain their current
theme.
- The application-wide `MotionPolicy` offers `Full`, `Reduced`, and `Disabled`
modes. Reduced mode keeps short finite transitions while suppressing
continuous motion; Disabled mode settles animations immediately. Full
remains the default, so existing applications keep their prior timings.
- C++ and PySide6 expose the same theme and motion choices. The Gallery settings
page makes both preferences directly testable, and changing a local animation
switch while a transition is running now settles that component immediately.
- The legacy boolean `ThemeRegistry` palette overloads remain available but are
deprecated in favor of the theme enum, which cannot silently collapse High
Contrast into Light.

Gallery and browser parity

- The C++ and Python Galleries present matching theme and motion settings and
use the public library APIs rather than Gallery-only styling.
- The Python Gallery keeps accepted local activation sockets alive through the
disconnect drain window, preventing missed single-instance reactivation on
Windows ARM64.
- The WebAssembly Gallery accepts Light, Dark, and High Contrast through its URL
and message bridge, honors browser forced-colors, and restores the user's
selected theme when forced-colors ends.
- The bilingual project website cycles through all three themes, follows the
browser's reduced-motion preference for site effects, and keeps its embedded
C++ Gallery synchronized.

Text input polish and fixes

- A visible, focused `TextEdit` now animates content-driven growth and collapse
between its configurable minimum and maximum visible-line bounds. Continued
editing retargets the active transition; Reduced and Disabled modes resolve
it through the same global policy.
- Programmatic text and layout-metric setters still reach their final geometry
synchronously. IME preedit leaves the wrapper stable until composition
commits, and crossing the scrolling threshold no longer interrupts an active
height transition.
- `AutoSuggestBox` refreshes filtered results after its model resets, so callers
no longer need to re-enter the query to see replaced data.

There are no breaking runtime API changes in this release.

[Compare v1.7.6...v1.8.0](https://github.com/calvinhxx/Fluent-Qt/compare/v1.7.6...v1.8.0)

<!-- docs-nav:bottom:start -->
---
[Contents](../SUMMARY.md) · [Releases index](README.md)
<!-- docs-nav:bottom:end -->

command, and tab behavior stable while removing duplicated implementation, and
strengthens the validation and release paths that protect published artifacts.

Component consistency and accessibility

- Multi-select combo boxes now join selected labels with the ideographic comma
`、`, so mixed English and Chinese interfaces no longer show an unexpected
translated conjunction.
- Date and time pickers now share one wheel interaction and painting contract,
while command bars and command-bar flyouts retain their distinct overflow
rules through a common projection model.
- TabView centralizes selected-tab curves and separator geometry, preserves the
existing pixel profile, and gives visible icon-only add, scroll, and close
buttons meaningful accessible names.
- ComboBox keeps its flyout implementation private instead of exposing internal
popup dependencies through the installed header surface.

Faster, stricter engineering gates

- Pull-request validation can build and run only the affected component test
groups, while broad or untrusted path changes still fall back to the complete
C++ suite.
- Changed C++ files are checked against the repository formatting contract;
missing base history and malformed test selections fail closed instead of
silently skipping validation.
- Tests link Qt Network only where it is used, reducing unnecessary build work
without changing runtime dependencies.

Release and community integrity

- Privileged publishing and Qt setup actions are pinned to reviewed immutable
revisions, manual release inputs are isolated from shell source, and the
WebAssembly toolchain is tied to an audited Emscripten revision.
- GitHub Pages deployment is restricted to authorized `main` artifacts and
verifies the downloaded WebAssembly payload against the current commit before
publication.
- The legacy Gallery URL remains available for existing links, and the Chinese
community guide now includes the official QQ developer group invitation.

There are no breaking runtime API changes in this patch release.

[Compare v1.7.5...v1.7.6](https://github.com/calvinhxx/Fluent-Qt/compare/v1.7.5...v1.7.6)

<!-- docs-nav:bottom:start -->
---
[Contents](../SUMMARY.md) · [Releases index](README.md) · [Fluent-Qt 1.7.5 →](v1.7.5.md)
<!-- docs-nav:bottom:end -->

keeps Gallery examples aligned across C++, Python, and WebAssembly, and adds
stronger evidence gates for AI-assisted GUI delivery.

Consistent component typography

- Buttons, hyperlink buttons, toggle switches, date pickers, and time pickers
now share the same semantic `fontRole` behavior.
- Theme-driven fonts continue to follow runtime family and scale changes, while
an explicit `setFont()` remains a caller-owned override.
- Picker flyouts preserve their pending values, focus, and layout while theme
typography changes are applied.

Cross-runtime Gallery confidence

- Changed Gallery samples now carry matching interaction and presentation
semantics across the compiled C++, PySide6, and WebAssembly runtimes.
- Cross-platform verification covers popup controls, ToggleSwitch hit geometry,
and size-to-content TabView labels without relying on one host's rendering.
- Gallery verification reports retain deterministic interaction evidence and
distinguish registered checks from independently reviewed visual approval.

AI delivery and maintenance gates

- The packaged `build-fluentqt-gui` Skill now owns the end-to-end workflow from
project analysis and implementation through launch, visual refinement, and
independent review.
- Public API policy and visual-evidence inventories fail closed when component
contracts or high-risk GUI coverage drift.
- CI change classification falls back to the full validation path when a pull
request cannot be safely treated as documentation-only.

There are no breaking runtime API changes in this patch release.

[Compare v1.7.4...v1.7.5](https://github.com/calvinhxx/Fluent-Qt/compare/v1.7.4...v1.7.5)

<!-- docs-nav:bottom:start -->
---
[Contents](../SUMMARY.md) · [Releases index](README.md) · [Fluent-Qt 1.7.4 →](v1.7.4.md)
<!-- docs-nav:bottom:end -->

improves several desktop interaction details, and makes local validation more
predictable.

Reliable GUI verification

- Native Gallery previews can execute declared pointer, keyboard, focus, and
state actions against real controls before capturing evidence.
- Versioned reports now include interaction results, named widget geometry,
Inspector findings, and a capture-environment fingerprint.
- The GUI verification runner checks required Light/Dark, width, and input
states, compares approved full-frame and high-risk-region pixels, and keeps
missing baselines or independent review in an explicit human-required state.
- Approved baseline bundles bind the pixels, capture report, scenario contract,
environment, and independent approver instead of silently accepting a new
screenshot.

Components and Gallery behavior

- Menu and MenuBar access keys remain reliable while menu animations settle or
are interrupted.
- Multi-select popup behavior and Gallery status presentation remain readable
across the refined interaction states.
- Parent-painted collection surfaces retain their intended Fluent appearance.
- Gallery test targets reuse their compiled shared sources to shorten repeated
local builds.

Development and delivery

- Local builds choose bounded parallelism from available CPU and memory while
retaining explicit overrides for reproducible constrained hosts.
- Reader documentation has a generated navigation tree and a cross-platform
validation gate, including Windows path handling.
- Release candidate and stable publication checks reuse commit-bound artifacts
while preserving the full desktop and Python validation contracts.

There are no breaking runtime API changes in this patch release.

[Compare v1.7.3...v1.7.4](https://github.com/calvinhxx/Fluent-Qt/compare/v1.7.3...v1.7.4)

<!-- docs-nav:bottom:start -->
---
[Contents](../SUMMARY.md) · [Releases index](README.md) · [Fluent-Qt 1.7.3 →](v1.7.3.md)
<!-- docs-nav:bottom:end -->