On Jan 25, 2008 2:48 PM, Mikko Rantalainen [EMAIL PROTECTED] wrote:
It's wise to always trying to minimize the battery usage in a battery
operated device. However, if the device is already using wireless or
wired communication for transmitting the data set it cannot just do
nothing.
from my
Hello,
Apologies in advance if I've missed these details in the specification.
The video element supports width and height. Does this include the
additional area needed (if necessary) by the controls? It strikes me that it
shouldn't, since it would be odd for the video width and height to
Michael(tm) Smith wrote:
Jerason Banes [EMAIL PROTECTED], 2008-01-25 23:41 -0600:
Long story short, accesskeys were an idea that worked better on paper than
they did in practice. They inevitably interfered with normal browser
operation as well as other accessibility features in such a way
Hi Charles,
It was my understanding that video controls should be able to be added
through style sheet mechanisms. Thus, there is no pre-set
specification, but it is rather left to the web page designer. The
javascript API will allow to hook up the controls with the video
player. The controls
On Mon, 28 Jan 2008 10:02:26 +1100, Matthew Paul Thomas
[EMAIL PROTECTED] wrote:
Michael(tm) Smith wrote:
Jerason Banes [EMAIL PROTECTED], 2008-01-25 23:41 -0600:
...
Another long story short: accesskey mark is already in use in a
significant amount of existing content, so leaving it
Hi Vlad,
as I read these, Opera is doing the right thing. Since the SVG you use
doesn't have a viewBox attribte to say how the thing should fit, it
creates an initial viewport where the size in px that the image element
gets corresponds to a view in SVG user units. So a 300x100 img shows a
