Instrument notification wake-up chain and widen polyfill coverage#441
Open
theoden8 wants to merge 1 commit into
Open
Instrument notification wake-up chain and widen polyfill coverage#441theoden8 wants to merge 1 commit into
theoden8 wants to merge 1 commit into
Conversation
6a239f3 to
58fd587
Compare
The OS-scheduler -> reload -> page JS -> webNotification -> show chain failed silently at every hop, forcing slow manual testing. Add trace logging across the Dart orchestration and the iOS/Android native bridges (aggregate counts and lifecycle only, no per-site metadata), plus dev-tools "Simulate background refresh" and "Send test notification" buttons so the chain can be exercised in the foreground without waiting on BGAppRefreshTask / WorkManager. Also cover page-context ServiceWorkerRegistration.showNotification (a common pattern the constructor-only polyfill missed) and emit console breadcrumbs when a notification is suppressed. True server-driven web push via the worker push handler stays out of reach by design; document that in the spec. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01296hFrdpF98B9MiqG83zMr
58fd587 to
1c2fd36
Compare
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
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.
The OS-scheduler -> reload -> page JS -> webNotification -> show chain
failed silently at every hop, forcing slow manual testing. Add trace
logging across the Dart orchestration and the iOS/Android native bridges
(aggregate counts and lifecycle only, no per-site metadata), plus
dev-tools "Simulate background refresh" and "Send test notification"
buttons so the chain can be exercised in the foreground without waiting
on BGAppRefreshTask / WorkManager.
Also cover page-context ServiceWorkerRegistration.showNotification (a
common pattern the constructor-only polyfill missed) and emit console
breadcrumbs when a notification is suppressed. True server-driven web
push via the worker push handler stays out of reach by design; document
that in the spec.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01296hFrdpF98B9MiqG83zMr