On Jan 26, 2008 11:57 AM, 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),; then
On Feb 10, 2008, at 12:41 AM, Robert O'Callahan wrote:
On Jan 26, 2008 11:57 AM, 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
On Sun, 3 Feb 2008, Anne van Kesteren wrote:
Why not give the object a constructor? I think that's cleaner. Also,
Opera already supports that :-)
The relationship between the height and width arguments and the height and
width of the ImageData structure returned can vary on a per-canvas
On Sat, 2 Feb 2008, Philip Taylor wrote:
On 31/01/2008, Ian Hickson [EMAIL PROTECTED] wrote:
I've made toDataURL() return data:, if it's faced with a 0-pixel image.
It's arbitrary, but I guess it represents the image, at least!
That makes the Note: When trying to use types other than
On Sun, 10 Feb 2008 10:21:34 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
On Sun, 3 Feb 2008, Anne van Kesteren wrote:
Why not give the object a constructor? I think that's cleaner. Also,
Opera already supports that :-)
The relationship between the height and width arguments and the height
On Sat, 09 Feb 2008 22:06:39 +0100, Alexey Proskuryakov [EMAIL PROTECTED]
wrote:
On Feb 9, 2008, at 12:58 PM, Anne van Kesteren wrote:
As far as the unload handler question, what are the semantics for XHR?
I think the user leaving the page is the same as aborting the download.
I've seen
On Sun, 3 Feb 2008, Anne van Kesteren wrote:
On Sun, 03 Feb 2008 10:43:10 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
On Fri, 25 Jan 2008, Oliver Hunt 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
On Feb 10, 2008 10:07 PM, Oliver Hunt [EMAIL PROTECTED] wrote:
That said, basically what you're saying is that canvas should not support
hidpi. At all. There is no need to request the dpi of a canvas, but (and
here's the critical bit) you can't have get/putImageData work at a different
On Sun, 10 Feb 2008 22:52:33 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
On Sun, 3 Feb 2008, Anne van Kesteren wrote:
The moment people start using getImageData() as storage mechanism
(which they will if browsers do not fix their data: image origin stuff)
you'll have a problem
So you want
On Feb 10, 2008, at 2:26 PM, Robert O'Callahan wrote:
On Feb 10, 2008 10:07 PM, Oliver Hunt [EMAIL PROTECTED] wrote:
That said, basically what you're saying is that canvas should not
support hidpi. At all. There is no need to request the dpi of a
canvas, but (and here's the critical bit)
On Feb 10, 2008 11:14 PM, Anne van Kesteren [EMAIL PROTECTED] wrote:
That would mean that passing ImageData around between two canvas
elements doesn't always work as expected. I think that's highly
undesirable. Is there any implementation where we know this will the case?
Not yet, but in
On Sun, 10 Feb 2008, Robert O'Callahan wrote:
So for ImageData, how about making the image data array have, by
default, one pixel value per canvas coordinate unit? If we really need
to expose a higher-resolution underlying buffer, then add an API to get
the device-pixel per
On Sun, 10 Feb 2008, Anne van Kesteren wrote:
On Sun, 10 Feb 2008 10:21:34 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
On Sun, 3 Feb 2008, Anne van Kesteren wrote:
Why not give the object a constructor? I think that's cleaner. Also,
Opera already supports that :-)
The relationship
On Feb 11, 2008 11:49 AM, Ian Hickson [EMAIL PROTECTED] wrote:
If we have one API, high-res only:
People who use it correctly:
get good results both today and tomorrow.
People who use it wrongly:
get good results today.
will get cropped or visibly wrong results tomorrow.
I've already tried to comment on this issue [1] but I think I haven't
achieve to make my point clear.
When developing a web application I can't usually rely on the languages
configured on the user browser (sent through the Accept-Language).
Often I need to send e-mail or sms notifications and I
On Feb 10, 2008, at 2:53 PM, Robert O'Callahan wrote:
On Feb 11, 2008 11:37 AM, Oliver Hunt [EMAIL PROTECTED] wrote:
On Feb 10, 2008, at 2:26 PM, Robert O'Callahan wrote:
On Feb 10, 2008 10:07 PM, Oliver Hunt [EMAIL PROTECTED] wrote:
That said, basically what you're saying is that canvas
On Feb 10, 2008, at 3:08 PM, Robert O'Callahan wrote:
On Feb 11, 2008 11:49 AM, Ian Hickson [EMAIL PROTECTED] wrote:
If we have one API, high-res only:
People who use it correctly:
get good results both today and tomorrow.
People who use it wrongly:
get good results today.
On Feb 11, 2008 1:05 PM, Oliver Hunt [EMAIL PROTECTED] wrote:
i was thinking having a style property, say, canvas-dpi: auto|device or
something, where the default auto value automagically does the evil
downsampling the moment a data routine is used, and device would result in
the right thing.
If, 5 years from now, most Web developers have 200dpi screens so
browsers are using at least a 2:1 ratio for their canvas backing
stores, then putImageData and getImageData could be safely
introduced with the current spec, because an assumption that device
pixels are the same as canvas
On Feb 10, 2008, at 5:44 PM, Robert O'Callahan wrote:
On Feb 11, 2008 1:05 PM, Oliver Hunt [EMAIL PROTECTED] wrote:
i was thinking having a style property, say, canvas-dpi: auto|device
or something, where the default auto value automagically does the
evil downsampling the moment a data
On Feb 11, 2008 12:51 PM, Oliver Hunt [EMAIL PROTECTED] wrote:
and the cost of sub-/super-sampling removes the whole speed thing
that the API was originally added for.
Not so sure about this. Script manipulation of pixel data probably isn't
going to be faster than native, probably
If this means that it would become possible to put a
dashed line through text at approximately x or m
height, I'm for it, too.
It would make it a lot easier to build certain kinds
of teaching materials for the lower primary grades,
where some kids need the center line to drag their
attention to
On Sat, 13 Nov 2004, Henri Sivonen wrote:
Anyway, I do think it's a problem for styling, automatic content
extraction and non-CSS presentation that HTML lacks the markup for
indicating which parts of the page are content proper and which are
navigation and other chrome. Therefore, a
23 matches
Mail list logo
