Hi ChrisThomas and Logos,
This is also interesting to read. Girorgi Maone mentions about NoScript not blocking- the UI glitch for the <video>-tag blocker (N.B.
and that could be unwanted behavior in the case of malcode:
They've put an absolutely positioned invisible div (of CSS class video_overlay) right over the movie (and the placeholder), preventing any click from reaching it. [bold by me]
I'm trying to work around, but I'm not sure if it's worth the effort.
Not <VIDEO> element specific, anyway, even though this is probably an artifact of the way some web authors are going to implement contextual menus over <VIDEO> elements in HTML5.
Then later he states:
Greatly mitigated in latest development build 1.9.5.7 Giorgio Maone -- Hackademix
And that is what I like, no obscurities, not hiding the obvious in plain site....that is why standards is for loosers....When I click the download buttons inside a WinCustomize dialog, Firefox is handling the downloads ... - Adds a Full Screen option to the context menu for HTML5 videos....
Another question for which I did not get an answer to here is what if GoogleChrome for watching video's would become
the standard, wouldn't that not also mean an enormous boost for that particular browser? Aren't we realizing now that Fx is fighting a battle to keep up with developments and that IE is forced to encapsulate GoogleChrome to be part of it. All these are very elaborate moves in the browser positioning chess-game (sorry video-game). I think the threads here are very informative in this respect as they give the dry and dirty facts on this...
polonus