-- Forwarded message --
From: Glyn Wintle [EMAIL PROTECTED]
Date: 25 Jan 2008 01:15
Subject: [ORG-discuss] BBC video codec to become an international standard
To: Open Rights Group open discussion list
[EMAIL PROTECTED]
First linked to by groklaw
So I came across this wonderful piece of javascript:
http://jsmsxdemo.googlepages.com/jsmsx.html
If present it uses putImageData (and getImageData to get the ImageData
object, which isn't required by html5 now -- and i think hixie was
look at doing some more work with ImageData).
With the
On Jan 25, 2008, at 6:56 AM, Oliver Hunt wrote:
With the current model for putImageData there is no way for them to
specify a dirty rect, which means their only option is to update the
entire display -- they have to copy the entire buffer.
snip
Anyway, i was thinking we would just need
In the present standard you are alowd to use the same accesskey in to
different links... For example:
a href=bob.html accesskey=bBob web page/a
a href=bob.html accesskey=bBob web page/a
But what would happend if this was to happend:
a href=bob.html accesskey=bBob web page/a
a href=alex.html
Why are there removing accesskey?
http://www.w3.org/TR/html5-diff/#absent-attributes
I though it was recommended to be used by WAI...
What are we should we use? Because its not said what accesskey is replace
with...
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 as to *
reduce* the accessibility of many web pages.
The intended replacement is the
I have to agree CSS would be the best way.
But is it rely use full to have in CSS order:... Could you just do it with
JavaScript...
I think that we should add new properties to CSS but I don't think its a
good idea to over load CSS with every new properties that we come up with,
that we
On Fri, 25 Jan 2008 23:57:56 +0100, Oliver Hunt [EMAIL PROTECTED] wrote:
Another thing that we need is some way to determine what the device
pixel-css pixel ratio is. Currently there's isn't even a real way to
tell that it's 1:1 -- you would have do do a fillRect(width-1, height-1,
1, 1),;
On Fri, 25 Jan 2008 23:56:28 +0100, Maciej Stachowiak [EMAIL PROTECTED]
wrote:
getImageData/putImageData will definitely cause problems for high-DPI
displays in the future that are driven with a scale factor where CSS
pixels are not device pixels. The question is whether it's better for
On Jan 25, 2008, at 2:30 PM, Anne van Kesteren wrote:
On Fri, 25 Jan 2008 21:00:41 +0100, Oliver Hunt [EMAIL PROTECTED]
wrote:
[...]
I had a question as I still think ImageData should be simplified.
Are you planning to support high resolution ImageData objects? As
specified ImageData
timeless wrote:
On 1/24/08, Mikko Rantalainen [EMAIL PROTECTED] wrote:
I think that WF2 section 5.6
(http://www.whatwg.org/specs/web-forms/current-work/#methodAndEnctypes)
should be modified to say something along the lines
User agents with interactive user interfaces should inform the user
Hi Charles,
Thanks for looking into this. Here you go:
http://xhtml.com/misc/svg-img1.htm
http://xhtml.com/misc/svg-img2.htm
http://xhtml.com/misc/svg-img3.htm
Regards,
-Vlad
http://xhtml.com
Original Message
From: Charles McCathieNevile
Date: 2008-01-24 10:47 PM
Hi Vlad,
Another thing that we need is some way to determine what the device
pixel-css pixel ratio is. Currently there's isn't even a real way to
tell that it's 1:1 -- you would have do do a fillRect(width-1,
height-1, 1, 1),; then getImageData(width-1, height-1, 1, 1) and see
if they match.
To add to what Christoph is saying, perhaps there's a better way to look at
this problem? A reverse list has both a start and an end, just like any
other list. The key is that it's displayed in the opposite order of a
regular list.
This raises the question, why does the list need to be
Simon Pieters:
It was pointed out to me that the start='' attribute (and the
corresponding DOM attribute) currently defaults to 1. This could,
AFAICT, reaonably trivially be changed to make it depend on the
direction of the list and the number of li children.
Or you would introduce an
On Jan 25, 2008, at 6:53 AM, Adam Roben wrote:
On Jan 25, 2008, at 6:56 AM, Oliver Hunt wrote:
With the current model for putImageData there is no way for them to
specify a dirty rect, which means their only option is to update
the entire display -- they have to copy the entire buffer.
16 matches
Mail list logo
