jgamboaandClaude
fe75904872
.window's 6px radius and its outer drop shadow are painted by the webview OUTSIDE the window's own rectangle, so on an opaque surface they were simply clipped — square corners, no shadow. chromeOptions now passes `transparent: true`, the page paints no background of its own, and .window takes a 6px margin as the gutter the shadow falls into (h-screen shrinks by the same amount so the gutter does not produce a scrollbar). Confirmed on Linux/WebKitGTK in a real run, which is the half the Firefox harness cannot model: GTK: Created window without decorations (custom titlebar) GTK: Created transparent window GTK WebKit: Applied transparent background to webview Also caught by the run rather than shipped: `transparent` is set in chromeOptions, which openSecondaryWindow spreads too — so the editor and connection-manager windows became transparent while still rendering bare content, i.e. floating widgets on nothing. Both roots now take the same .window.glass frame and their own windowFocused signal. The editor's blur binding had to merge with the existing flushDraft() call; a duplicated host key is a TS1117 build error rather than a merge, which is how it surfaced. The old anti-flash <style> in index.html is gone with the opaque backgrounds it guarded — windows are created hidden and revealed on dom-ready anyway. Not handled yet: a maximized Win7 window has no radius, shadow or gutter. The 6px margin currently applies in every state. Co-Authored-By: Claude <noreply@anthropic.com>
Ui
This project was generated using Angular CLI version 22.0.6.
Development server
To start a local development server, run:
ng serve
Once the server is running, open your browser and navigate to http://localhost:4200/. The application will automatically reload whenever you modify any of the source files.
Code scaffolding
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-name
For a complete list of available schematics (such as components, directives, or pipes), run:
ng generate --help
Building
To build the project run:
ng build
This will compile your project and store the build artifacts in the dist/ directory. By default, the production build optimizes your application for performance and speed.
Running unit tests
To execute unit tests with the Vitest test runner, use the following command:
ng test
Running end-to-end tests
For end-to-end (e2e) testing, run:
ng e2e
Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Additional Resources
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.