yes and no
Originally Posted by Ryoga2k
it's the useragent, as in the agent/browser triggers the html5 test and results are slightly different depending on the kind.
it's not the useragent, as if the check returns html5 compliant, it checks the cookie for a specific value to see if opted in or not to use html5 as player.
Bottom line, a cookie patch, or a config variable in the browser.conf file similar to the firefox workaround, would be cleaner solutions.
Maybe(surely) there are more variables that can be set in the browser config files, and maybe one disables the html5 playback