FPS Policy
The District’s rules for browser windows, tabs and downloads on student Chromebooks, set by the Technology Department.
FPS Policy applies a short list of rules about how the browser is used — things a web filter cannot see because they are about windows and tabs, not web addresses. Each rule is either off or block, and the Technology Department decides which are on. Every rule starts off.
When a rule blocks something, the tab shows a short page explaining why.
- Limit browser windows — an extra window is folded back into the first one.
- Pop-up windows become tabs — a floating pop-up becomes an ordinary tab. Sign-in pop-ups are left alone.
- Limit open tabs, and tabs opening too fast — stops a page that opens tabs in a loop.
- Games hidden in a blank tab — a web site loaded inside an about:blank or blob: tab.
- Tabs disguised as Google apps — a page that names itself, or uses the icon of, Google Docs, Classroom, Drive or Gmail while not being Google.
- History flooding — a page that piles up Back-button entries faster than a person could.
- Saving game files — downloads of web-page and Flash files.
Getting it
Installed automatically by the Technology Department on student Chromebooks, one school at a time. It is not installed on staff accounts.
Questions
Does it report what I do?
No. FPS Policy checks tabs, windows and downloads on the Chromebook itself and sends nothing back — not to the District, not to anyone.
A page I need for class was blocked.
Note the address and tell your teacher, who can pass it to the Technology Department.
What’s new
0.1.0
- First version: limit windows, pop-ups become tabs, limit tabs, tabs opening too fast, games hidden in a blank tab, tabs disguised as Google apps, history flooding, saving game files. All off until switched on.