ZacharyZhang-NY
7b2b6daee9
After840255fput the input overlay on-screen anda80d039dropped the file-system pixel pipe, the two harness baselines confirm: * `.occlude() + capture_any_mouse_up` works in TestAppContext (baseline_overlay_div_receives_simulated_click) * `input_overlay`'s exact listener combo works in isolation (baseline_overlay_with_full_listener_combo_receives_click) …and the layout regression guard confirms the overlay is now drawn inside the visible window. Yet running a real ElyShell, navigating to https://example.com/, and dispatching a real MouseDown/MouseUp at the geometric center of the measured viewport STILL leaves WebSurfaceStore.click_point as None. The capture phase listener is being eaten somewhere strictly inside the real ElyShell widget tree. `user_click_in_rendered_web_canvas_reaches_input_pipeline` encodes this contract in user terms — "click on the rendered page and the input pipeline records it" — without naming a GPUI mechanism. The test is marked `#[ignore]` so the rest of the suite stays green; the attribute carries the full reproduction note so a reader picking the ticket up later doesn't have to rediscover what we already know (layout + pixel-pipe both clean, listener combo clean, suspicion now on sibling z-order / ancestor stop_propagation / overflow_hidden content_mask clipping the overlay's hitbox). The fix commit must DELETE the attribute outright; toggling the ignore reason is a broken contract. Running `cargo test -- --ignored user_click_in_rendered_web_canvas_reaches_input_pipeline` today reproduces the failure with click_at = (1106, 567) inside viewport_bounds (309, 71, 1594, 992). cargo test --bin ely_app: 112 passed, 0 failed, 1 ignored. cargo test --bin ely_app -- --ignored: 1 failed (expected RED).
ELY Browser
Native Rust + GPUI browser workspace for ELY Browser by Elydora.
The repository is organized around explicit product boundaries from PRD.md:
domain state, browser orchestration, design tokens, GPUI shell, and Servo host contracts.
Reference GPUI ecosystem repositories live under references/ for local review and are excluded
from version control.
Local Commands
cargo fmt --all --check
cargo check --workspace --all-targets
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --all-targets
cargo check -p ely_servo_host --features servo-engine --all-targets
cargo clippy -p ely_servo_host --features servo-engine --all-targets -- -D warnings
cargo test -p ely_servo_host --features servo-engine --test software_host
scripts/verify_prd_site_rendering.sh
scripts/verify_windows_app_manifest.sh
cargo run -p ely_app
Cloudflare Auth Configuration
/api/auth/* is served by Better Auth in the Cloudflare Worker. Local wrangler dev
uses ELY_AUTH_BASE_URL from cloudflare/wrangler.toml; deployed environments should
set the matching public Worker origin.
Use Wrangler secrets or an untracked cloudflare/.dev.vars file for the remaining auth
bindings:
wrangler secret put ELY_AUTH_SECRET
wrangler secret put ELY_AUTH_GOOGLE_CLIENT_ID
wrangler secret put ELY_AUTH_GOOGLE_CLIENT_SECRET
wrangler secret put ELY_AUTH_GITHUB_CLIENT_ID
wrangler secret put ELY_AUTH_GITHUB_CLIENT_SECRET
wrangler secret put ELY_AUTH_EMAIL_OTP_ENDPOINT
wrangler secret put ELY_AUTH_EMAIL_OTP_TOKEN