Skip to content

WaEnhancer Community 0.0.13

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Oct 16:29
v0.0.13
b079ae2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

WaEnhancer Community 0.0.13

SHA-256: 041422d021e61caeb682343c84acd9beab1b424ae17d64d46f974b74eb837d26

Changes since v0.0.12.

What's changed

  • #81 fix(glass): home rows behind the search pill with Search only; keep the header fill clear

Full changelog

This section compiles the descriptions of the pull requests included in this release.

#81 — fix(glass): home rows behind the search pill with Search only; keep the header fill clear

Merged by contribution from @igorcv88.

Problem

  • With only Search on, nothing scrolled behind the search pill.
  • With only Headers on, the header capsule showed no rows behind it.

Changes

  • Search only: HomeGlassChrome used to extend the list only when Headers was on. It now extends it when either Headers or Search is on. The header fill is cleared only when Headers is on, and restored when Headers is turned off while Search stays on.
  • Headers only: reading the screenshot pixels, the native pill is translucent (about 9.5 % white), so the list extension and the Z raise already work. The header capsule, though, shows the plain app background, and the row is cut flat at the header's bottom edge. So something opaque sits under the toolbar glass. The prime suspect is WhatsApp's lift state, which swaps or recolours the toolbar_container fill on scroll without a layout; sync runs only on global layout, so it never sees that. A new HomeGlassChrome.frame() runs in the window pre-draw before captures:
    • it re-clears a fill that was replaced, and resets our replacement if it was recoloured;
    • it logs HOME_CHROME header-chain whenever the chain changes, so the next device log either confirms this cause or names the actual opaque layer.

Not established

The cause of the Headers-only bug isn't proven yet. The log from the device will settle it.

Validation

  • :app:testWhatsappDebugUnitTest: 425 tests, 0 failures.
  • :app:assembleWhatsappDebug: succeeds.
  • Not tested on the device yet.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JN7ZPJjeqP3W2AQTAUUuvr

Assets 5
Loading