Refused is not unavailable: inspect accepted/refused/unavailable bridge outcomes
refused differs from unavailable; accepted is not a backend handling receipt
collieBridgeScript checks origin/full pageURL/visibility and observes detail reads, accepted writes and event cancellation. It returns accepted/refused/unavailable. Native handling continues to guarded DOM only for explicit unavailable, not refusals, exceptions or arbitrary results. accepted is a protocol report, not sending or business completion.
Different from origin, reservations and completion review
Origin concerns boundaries, reservations concern attempts, auditing concerns results. Here optional page-bridge observation and permission to try the next adapter branch matter. No event injection, fake bridge or global-page modification occurs.
| Check | Verified scope | Manual review | Not established |
|---|---|---|---|
| Preconditions | Origin/pageURL/hidden etc. | Actual page/phase | Same title implies trust |
| accepted | Explicit accepted=true wins | Host report versus target content | Server received/executed/approved |
| Observed | Reads text/accepted or writes accepted | Protocol consumption | All site capabilities scanned |
| refused | Without accepted, observed/defaultPrevented etc. | Refusal/boundaries | Treat as absent and bypass |
| unavailable | No observed protocol handling | Only this permits next DOM attempt | No capability anywhere on the page |
| DOM continuation | allowed/adapter guards remain | Focus/draft/page/request | Unconditional writing/sending |
| Exception/unknown | Not automatically unavailable | Effects/unknowns retained | Definitely no write, safely replay |
| Receipt layers | Isolated Bool receipts differ from page bridge | Actual layer/outcome | Any non-Bool means sent |
Synthetic bridge note
refused: stop rather than relabel unavailable to try another composer. accepted: report protocol acceptance, inspect actual content, and do not invent sent/executed. No real handoff ran.
The native path makes no submit call, but arbitrary site behavior is not certified. Protocol observation is not scanning, account identity or universal idempotency. Compatibility cannot justify fake bridges or changing locks/sending state.
FAQ
Can refused be treated as absent bridge?
No. Native refusal does not continue DOM fallback.
Does unavailable prove no site capability?
No. It is this observed protocol outcome; later adaptation remains guarded.
Does accepted prove business handling?
No. Acceptance, placement, sending, receipt and handling differ.
Does preventDefault always override accepted?
No. accepted=true wins; otherwise cancellation can yield refused.
Can exceptions trigger another composer/replay automatically?
Do not blindly downgrade/replay; retain unknown request/target state.
Was a bridge configured/tested?
No. Fixed protocol review only, without page changes/services.
Reading and source
Page/origin · One handoff · Completion evidence · Start · Privacy
