net::ERR_BLOCKED_BY_CLIENT firestore.googleapis.com
```[cite: 4, 5]
This occurred because the file was running locally as `file:///Users/...` on your desktop[cite: 4, 5]. Modern browsers treat `file:///` as an untrusted origin[cite: 4, 5]. Ad blockers, privacy tools, and even Chrome’s built-in shield see background data streaming from a raw desktop file to a third-party Google server and immediately sever the connection for security[cite: 4, 5].
As long as we run it as a double-clicked file off your desktop, browser security will keep blocking that background sync[cite: 4, 5].
### How we solve it
The moment this file is served over a real web address (`https://`), the browser treats it as a legitimate web application, and that blocker error disappears.
Here is the plan to get the exact hub you liked back up and working:
1. **Restore all previous features:** We keep the original layout, the dual document dropzones, the in-browser PDF/Word (`.doc`/`.docx`) rendering, team identity switching, notes, and direct Firebase sync.
2. **Put it directly on Cloudflare Pages:** Instead of testing it on the desktop where Chrome blocks the connection[cite: 4, 5], we deploy the file to Cloudflare Pages (which takes under 60 seconds).
3. **Test live:** You open `[https://your-hub.pages.dev](https://your-hub.pages.dev)` in Chrome and Safari. Because it runs on HTTPS, the database connects without being blocked, and you get real-time syncing and document handling across all 3 team members.
Below is the complete code for the original version with all features intact and your Firebase keys configured:
```html
TenderHub - Procurement Workspace
TenderHub
Connecting to Cloud...
Active As:
> 7 days 3-7 days < 3 days Expired Yellow outline: Submitted