Repository navigation
fix(permissions): expose PermissionStatus as EventTarget - #1503
lanyue-llk wants to merge 1 commit into
Conversation
Sequential Navigation Soak A/B✅ HEAD completed the 200-navigation resilience and memory observation. One browser process, one target, and one CDP session navigate CSDN → SegmentFault → Huaban → example.com repeatedly. This run issued 200 Common ancestor Session resilience
A public-page failure is reported separately from an unrecoverable session. The soak requires all navigation attempts, zero failed recovery, zero lifecycle/network ordering violations, and complete resource evidence. Process-tree memory
HEAD memory by 50-navigation quarter
Raw reports and per-navigation boundary samples: workflow run and full Public-site timing and memory are observational. Use the A/B deltas and trend shape as evidence, not as a deterministic performance threshold. |
|
Closing this to keep the Web Fetch correction effort scoped to the consolidated renderer fixes in #1501. The PermissionStatus/EventTarget change is a valid independent standards improvement, but it is unrelated to the measured Web Fetch regressions and is not required by the current evidence. It can be reopened or resubmitted when that product behavior is independently prioritized. |
Problem
PermissionStatusexposesonchange, but its generated prototype does not inherit fromEventTarget. Instances therefore cannot use the standardaddEventListener,removeEventListener, ordispatchEventAPIs.Result
PermissionStatusas anEventTargetsubclass.once, callback targets, and the non-constructible interface.This PR only supplies the standard event interface. It does not claim that permission state changes are emitted automatically.
Validation
cargo fmt --all -- --checkpermission_status_supports_inherited_event_target_listenersThis replaces the independent permissions portion of #1476. Its Web Fetch changes are superseded by #1501.