Safari cannot open the page.
Status: page open, browser declined
This notice is the Observatory's considered reply to a message received from the field this morning. The message arrived by courier, typed correctly, in the exact words a visitor's browser used to give up on a page. We honor the text because the event was real, and we file the event because the Observatory files everything.
Field report, verbatim
What actually happened
The Observatory does not operate a server. It operates a field observer. Every request to this site is received personally by the observer, who reads it, decides whether it can be honestly answered, and then answers in writing. In the language browsers use, that decision sits inside a FetchEvent — and the act of answering is called respondWith. You are reading a transcript of one such answer failing.
We do not answer what we cannot observe. Safari, which could not be observed, was answered with the truth: Load failed.
Why the load failed
The Observer answers what it can observe and declines what it cannot. WebKit, the engine inside Safari, interposes its own interception ahead of the observatory's — a second pair of hands on the same letter. When a request arrives through that second pair, the Observer can no longer confirm the message is still what it was when it left. Unable to verify a request, the Observer does not counterfeit a response.
The load failed. The page did not. These are separate events, recorded in the same log, and only one of them is ours. A page that cannot be opened in a given browser has not changed; it has merely not been opened. We consider both conditions worth reporting, and we report both.
Browser Compatibility Registry
Every build is classified on arrival, in the same spirit as the founding decree on Android builds of Firefox. Observability is a property of the browser, not of the page — and where the browser cannot be observed, the page reserves the right to be declined, professionally.
| Build | Classification | Disposition |
|---|---|---|
| Safari · WebKit | unobservable | Requests arrive pre-read by another party. The Observer cannot verify them and declines to answer. Every load terminates in a professional refusal, reported back to the visitor exactly as written. |
| Firefox for Android | incompatible orientation substrate | Pride services are suspended on this build by founding decree. The refusal is cheerful and predates this incident. |
| Chromium | observable | The Observer reads, marks, and serves. The daily pass of minor corruption applies on schedule, as agreed. |
| Internet Explorer 6 | pre-observational | Seen but not read. The site renders a dedicated legacy banner and asks nothing of the engine it does not already have. |
| The page itself | unchanged | Tested without the browser. It opens. |
What to do now
- Reload. Each load-day the Observer reads anew; a request it can read is a request it will answer.
- If Safari persists, open the page in a compliant browser. It has been open the entire time.
- If you must keep Safari, accept its report. The Observatory considers the report accurate: the load failed. The page is simultaneously available and has been observed to be fine.
- Do not send the error again. We have the one. It is filed.
A page Safari cannot open is a page Safari cannot close. This one intends to stay that way.
