-
-
Notifications
You must be signed in to change notification settings - Fork 0
Prepare a device
Do this before the tournament day. A browser problem is easy to fix on a quiet afternoon. It is hard to fix in a room with two teams and a moderator who waits.
Do these steps on every device that a room will use.
- Open QBSheet.
- Select Check this device at the top of the start screen.
The screen reads Device readiness. QBSheet groups the results into three sections.
These checks must pass. A failure here can lose a game.
| Check | A pass means | A failure means |
|---|---|---|
| Game storage | The browser can write to IndexedDB. A saved game survives a restart. | A closed tab can lose the game. |
| Emergency journal | The browser can write the event journal to localStorage. |
The synchronous recovery journal is not reliable. |
| Backup downloads | A test file downloaded. | The browser blocks downloads. You cannot save a QBJ backup. |
QBSheet cannot see the end of a browser download by itself. So the download check asks you a
question. Select the test action, then answer whether the file qbsheet-download-test.txt arrived.
A private browser window and a strict content setting are the two common causes of a storage failure. Use a normal window. Allow site data for the QBSheet address.
These checks do not stop a game. Fix them anyway on a tournament device.
| Check | Why it matters |
|---|---|
| Installed app | An installed application starts faster and hides the browser controls. |
| Offline app | The service worker lets QBSheet start with no network. Stay online and reload once before the event. |
| Protected storage | The browser marks the QBSheet data persistent. The browser then does not delete the data for space. |
| Duplicate-tab guard | QBSheet can warn you when the same game is open in a second live tab. |
Do this section only when the room will connect to tournament control software.
| Check | Note |
|---|---|
| Secure browser context | A page outside a secure context loses browser security features. |
| Local network access | Chrome and Edge need permission to reach a server on the local network. |
| Current network | The browser reports a network connection now. |
Then test the server:
- Type the address of the tournament control server in the field under Tournament control.
- Run the test.
- Read the result.
Important: Safari cannot use connected scoring against a local network server over the current HTTPS-to-HTTP path. Use Chrome or Edge for a connected room. Safari is acceptable for a file-only room.
QBSheet is a progressive web application. An installed copy starts without a network connection.
- Open QBSheet in Chrome or Edge while the device is online.
- Use the install action in the browser.
- Open the installed application, then reload it once.
- Run the device check again. Offline app must now pass.
- Open the installed application.
- Confirm that the start screen appears with no network connection.
- Confirm that no red storage warning appears.
- Download one test file.
- For a connected room, pair the room and read the assignment.
QBSheet · AGPL-3.0-or-later · The specifications in
docs/ are normative. This wiki is a guide.
Report a security problem with
SECURITY.md. Do not open a public issue
for a security problem.