Webplayer deliberately caping the framerate?

Can this behaviour be disabled? I am measuring frames per second at runtime and choose level of detail and render settings on the fly accordingly. Now with a fixed 32fps, my game always chooses the lowest level of graphics detail altough it could easily render it at the highest level in the webplayer (remember my standalone runs at 180 fps!!).

What are the capping numbers that depend on Browser and OS? What's the idea behind capping the frame rate depending on Browser on OS in the first place?

It can't be disabled. The way plugins work depends on the browser and OS so it's not entirely under Unity's control anyway.

So if frames per seconds do not represent actual workload, how can I adjust graphics settings at runtime dynamically? After all it is an extreme difference if someone's using a dedicated graphics card or just an onboard card a'la Intel GMA945 (extremely slow, yet the most widespread setup accordings to Unity Webplayer statistics).

Regarding "not under Unity's control": This must be a limitation of Unity. I can get the browser's window handle and render into the window using DirectX as fast as I want/the machine can. I don't understand the idea behind Unity's way of capping the frame-rate.

As I illustrated with Safari on OS X, different browsers on different OSs have different behavior. Firefox is clamped to 50fps, Safari isn't.

Again, is there concrete information what the capping values are for existing OS/Browser combinations? (e.g. Firefox 3.6.1 on my XP machine is capped to 32 fps in windowed mode and 64fps in fullscreen mode, not 50!)

Since I know neither Firefox nor IE pose any limitation on framerates, it's Unity's "fault".

This renders any automatic FPS based behaviour (like adjusting details on the fly) useless. So why does Unity do it? And why don't they cap it to the same value (at least on Windows)?