A test page for developing Yapbee. Nothing runs until you press a button, and every press writes its result in
the log at the bottom. Add this page as a web address Bee. The README lists what each control should do.
Notifications
Count and title
Sounds
Quiet tones made by the page. Open the page with ?autoplay=1 to test an attempt to play on load.
Camera and microphone
no live tracks
From a frame of another site (must be refused)
Links, pop-ups and moving on
Links log that they were pressed; Yapbee decides what happens.
Right-click here to try the context menu (the log says where). Select some of this text to try selection:
the quick brown fox jumps over the lazy dog, and then a second sentence to select.
Downloads and upload
Drop files here
Permissions (Yapbee must refuse all but fullscreen)
Each button asks once and shows granted, denied or the error.
A box for pointer lock and fullscreen.
Sign-in simulation
These open pages of this site (reached by a press). The back link comes back here.
Off until pressed. Every stress has a hard limit that the address cannot raise, a stop, and (where it runs
over time) a stop by itself. The address only fills the fields, for example
?cpu=80&mem=500&dom=200000&timers=2000¬ify=flood, so a Bee can be made with it.
CPU
not running. Stops by itself after 120 s.
Memory
not running. Lets go by itself after 120 s.
Page size
none
none
Timers, frames, requests, messages
not running. Stops by itself after 120 s.
not running. Stops by itself after 60 s.
not running
not running. Stops by itself after 30 s.
Notification storm
not running. Ask permission in the first section first.
Freeze and crash
No stop is possible while it is frozen: the limit of 15 seconds is the stop.
If the page does not crash by the limit, it lets go by itself.
Server routes (need the deployed lab; a plain file server answers 404)