The Canvas element itself can be styled with CSS ( borders, size, outlines,
background, ... ) but what is done in the CanvasContext does not end up in
the DOM tree and therefore their styling can not be affected using CSS.
--
Mathieu 'p01' HENRI
JavaScript developer, Opera Software
On Tue, Apr 8, 2008 at 11:37 AM, Greg Houston wrote:
Between Anne, Thomas and I, we have clearly shown that the individual
shapes within a canvas element can indeed be effected by CSS at the
time of their rendering and re-rendering(such as in an animation).
at the time of their rendering
Thomas Broyer wrote:
On Tue, Apr 8, 2008 at 11:37 AM, Greg Houston wrote:
Between Anne, Thomas and I, we have clearly shown that the individual
shapes within a canvas element can indeed be effected by CSS at the
time of their rendering and re-rendering(such as in an animation).
at the time
Dnia 08-04-2008, Wt o godzinie 12:39 +0200, Thomas Broyer pisze:
On Tue, Apr 8, 2008 at 11:37 AM, Greg Houston wrote:
Between Anne, Thomas and I, we have clearly shown that the individual
shapes within a canvas element can indeed be effected by CSS at the
time of their rendering and
On 5 Apr 2008, at 11:57 pm, Ian Hickson wrote:
On Sat, 5 Apr 2008, Christoph Päper wrote:
Should (or may) user agents display the content of the |title|
attribute
of an |a| element in the GUI window caption (if the window manager
used
supports such), when the user followed the link and
If users need to be able to restyle content in order to see it, how
would this work with Canvas? Should UAs provide daltonization
functionality for Canvas content, for example?
http://www.vischeck.com/daltonize/
--
Benjamin Hawkes-Lewis
On Tue, 08 Apr 2008 18:44:31 +0200, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
If users need to be able to restyle content in order to see it, how
would this work with Canvas? Should UAs provide daltonization
functionality for Canvas content, for example?
The spec for the add and remove ApplicationCache methods does not say
what to do about how relative URIs should be resolved.
I think it would be most intuitive to resolve them agains't the URI o
the document that the ApplicationCache object is associated with.
Comments?
Anders
I will take the responses as votes, and the nays overwhelmingly win.
Thank you for your consideration and debate.
In the sum, the primary reason against is that changes to the CSS
would not immediately effect the canvas drawing, which is the accepted
behavior of CSS, i.e., instant results.
The
Nicholas Shanks:
On 5 Apr 2008, at 11:57 pm, Ian Hickson wrote:
On Sat, 5 Apr 2008, Christoph Päper wrote:
Should (or may) user agents display the content of the |title|
attribute of an |a| element in the GUI window caption (...), when
the user followed the link and the retrieved resource
Section 4.10 has 2 details I'd like clarification on, that I think
will probably result in changes to the spec.
1 - The entire section describes the StorageEvent interface, and
specifies where StorageEvents should be fired when setItem() is called
on any Storage object. I asked the
Anders Carlsson wrote:
The spec for the add and remove ApplicationCache methods does not say
what to do about how relative URIs should be resolved.
I think it would be most intuitive to resolve them agains't the URI o
the document that the ApplicationCache object is associated with.
12 matches
Mail list logo
