On Jun 2, 2008, at 04:27, Benjamin Smedberg wrote:
Henri Sivonen wrote:
Firefox and Opera being able get away with not supporting EBCDIC
flavors suggests that EBCDIC-based encodings cannot be particularly
Web-relevant. Even if saying that browsers MUST NOT support them
might end up being
On Mon, 02 Jun 2008 05:26:40 +0200, Ernest Cline
[EMAIL PROTECTED] wrote:
The a element can already do this and it would be backwards
compatible.
Backwards compatible with some user agents but not with the specs.
Sure, but anchor is not backwards compatible with specs or user agents.
--
Ian Hickson wrote on 27/05/08 07:47:
On Mon, 12 Nov 2007, Matthew Paul Thomas wrote:
On Oct 30, 2007, at 6:01 PM, Ian Hickson wrote:
On Mon, 13 Jun 2005, Matthew Thomas wrote:
...
Many applications provide inline help which is not a label, and the
same attributes would be appropriate
Sorry it took me a bit to respond here... so, ok, based on the
discussion, I'd suggest:
- user-created ImageData-like objects should be supported, e.g. with
language such as:
The first argument to the method must be an ImageData object returned
by createImageData(), getImageData(), or
I'd like to propose adding an imageRenderingQuality property on the
canvas 2D context to allow authors to choose speed vs. quality when
rendering images (especially transformed ones). This is modeled on
the SVG image-rendering property, at
Um, could you actually give some kind of reasoning for these? I am
not aware of any significant performance issues in Canvas that cannot
be almost directly attributed to JavaScript itself rather than the
canvas.
--Oliver
On Jun 2, 2008, at 12:19 PM, Vladimir Vukicevic wrote:
I'd like
Sure; bilinear filtering is slower than nearest neighbour sampling,
and in many cases the app author would like to be able to decide that
tradeoff (or, at least, to be able to say I want this to go as fast
as possible, regardless of quality). Some apps might also render to
a canvas just
I like the idea of this property. I actually would love to see the
SVG property applied to HTML img as well. :)
dave
On Jun 2, 2008, at 4:15 PM, Vladimir Vukicevic wrote:
Sure; bilinear filtering is slower than nearest neighbour sampling,
and in many cases the app author would like to
Yeah, I agree -- I thought that there was some plan somewhere to
uplift a bunch of these SVG CSS properties into general usage? I know
that Gecko uplifted text-rendering, we should figure out what else
makes sense to pull up. (If image-rendering were uplifted, it would
apply to canvas,
On Jun 2, 2008, at 4:34 PM, Vladimir Vukicevic wrote:
Yeah, I agree -- I thought that there was some plan somewhere to
uplift a bunch of these SVG CSS properties into general usage? I
know that Gecko uplifted text-rendering, we should figure out what
else makes sense to pull up. (If
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering? It
should be the job of the platform to determine what level of
performance or quality can be achieved on a given device. Typically
such a property would
On Jun 2, 2008, at 2:39 PM, Oliver Hunt wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the platform to determine what level of
performance or quality can be achieved on a
On Jun 2, 2008, at 4:57 PM, Vladimir Vukicevic wrote:
On Jun 2, 2008, at 2:39 PM, Oliver Hunt wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the platform to determine
On Tue, Jun 3, 2008 at 9:34 AM, Vladimir Vukicevic [EMAIL PROTECTED]
wrote:
Yeah, I agree -- I thought that there was some plan somewhere to uplift a
bunch of these SVG CSS properties into general usage? I know that Gecko
uplifted text-rendering, we should figure out what else makes sense to
On Tue, Jun 3, 2008 at 9:39 AM, Oliver Hunt [EMAIL PROTECTED] wrote:
That's exactly what i would be afraid of people doing. If I have a fast
system why should i have to experience low quality rendering? It should be
the job of the platform to determine what level of performance or quality
On Jun 2, 2008, at 3:19 PM, Robert O'Callahan wrote:
On Tue, Jun 3, 2008 at 9:39 AM, Oliver Hunt [EMAIL PROTECTED] wrote:
That's exactly what i would be afraid of people doing. If I have a
fast system why should i have to experience low quality rendering?
It should be the job of the
-Original Message-
From: Anne van Kesteren [EMAIL PROTECTED]
Sent: Jun 2, 2008 5:39 AM
On Mon, 02 Jun 2008 05:26:40 +0200, Ernest Cline
[EMAIL PROTECTED] wrote:
The a element can already do this and it would be backwards
compatible.
Backwards compatible with some user agents but
17 matches
Mail list logo
