feat: polish dock behavior and extension review readiness - #81
Merged
Conversation
Introduce configurable dock motion profiles with isolated animation state, press feedback, and integration coverage for catalog and transform behavior. Keep Picture-in-Picture windows above normal windows and visible across workspaces while excluding them from dock smart reveal, including the cross-monitor focus case where PiP previously caused the dock to reappear. Expand Capture Tools with movable annotations, deterministic toolbar placement, and stronger unit and Shell integration coverage. Separate production and development extension entry points, modularize Just recipes, verify package contents, and keep developer-only tooling out of the production archive. Harden lifecycle cleanup across Shell modules, document accepted EGO analyzer findings, align metadata and documentation, and add policy checks for GNOME Extensions review readiness. Validated with type checking, linting, formatting, Shexli, 184 unit tests, 22 GNOME Shell integration tests, and production/development package inspections.
Attach both the production extension archive and the separate DevTool-enabled development archive to stable releases and manually dispatched release candidates. Apply the same two-asset policy to nightly pre-releases so QA and contributors can download the development build directly from every published release type. Document the purpose of each asset and keep the production archive as the recommended package for regular installations. Validated workflow YAML syntax, Prettier formatting, and staged diff integrity. The local QA acceptance document is intentionally excluded from this commit.
Replace fixed DevTool dock animation delays with condition-based polling so the integration test follows the actual Shell state under forced animations. Wait until the selected dock is hidden, its reveal state is cleared, and its hot area is reactive before triggering the simulated edge action. Also wait for show and reveal transitions instead of assuming fixed completion times. This removes the CI race where the pending rearm timer treated the DevTool trigger as a duplicate and then cleared hotAreaActive after the assertion started. Validated with just validate, the host DevTool integration test, and the Toolbox DevTool integration test; both integration runs passed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce configurable dock motion profiles with isolated animation state, press feedback, and integration coverage for catalog and transform behavior.
Keep Picture-in-Picture windows above normal windows and visible across workspaces while excluding them from dock smart reveal, including the cross-monitor focus case where PiP previously caused the dock to reappear.
Expand Capture Tools with movable annotations, deterministic toolbar placement, and stronger unit and Shell integration coverage.
Separate production and development extension entry points, modularize Just recipes, verify package contents, and keep developer-only tooling out of the production archive.
Harden lifecycle cleanup across Shell modules, document accepted EGO analyzer findings, align metadata and documentation, and add policy checks for GNOME Extensions review readiness.
Validated with type checking, linting, formatting, Shexli, 184 unit tests, 22 GNOME Shell integration tests, and production/development package inspections.