All,
I recently discovered that a common and well understood 2D graphics
operation is not supported by the 2D canvas API even though it is supported
by almost every other modern 2D graphics API. This missing feature is
called even-odd fill and controls how the fill region is calculated for
On Jan 2, 2013, at 3:40 AM, James Ascroft-Leigh j...@jwal.me.uk wrote:
All,
I recently discovered that a common and well understood 2D graphics
operation is not supported by the 2D canvas API even though it is supported
by almost every other modern 2D graphics API. This missing feature is
On 04/08/2011 05:05 AM, Lachlan Hunt wrote:
One option is to define that the list-style-type 'disclosure-*' as magic values
that mean to render a UA specific/platform
dependent widget. But that differs from all other list-style-type values and
doesn't seem quite right.
The CSSWG discussed
Hi James,
this features is not a trivial as it seems. Adding this will necessitate
updates to the algorithms that deal with paths and the outlining of strokes
and text.
As Dirk mentioned, instead of making it part of the graphics state, it's
more likely better to make it part of the fill or clip
Actually, fillRule was really trivial to implement since the underlying
graphics context already had that as a Boolean state attribute. All I
needed to do was expose the existing attribute through the canvas API IDL.
Take a look at the patch and notice how it doesn't actually add any new
On Wed, 2 Jan 2013, Cameron McCormack wrote:
I'm wondering if anybody has had any further thoughts on how summary
and details should be made stylable.
Like most widgets, I think the answer is Web Components.
--
Ian Hickson U+1047E)\._.,--,'``.fL
yes, your particular use case was easy.
However, just look at how stroke is implemented in the Canvas 2d spec or
how you can create paths by stroking or stroked text. They're all affected
by the winding rules.
(The description on how to do strokes in the spec is very wrong, but that
can be
On Wed, Jan 2, 2013 at 8:53 PM, Ian Hickson i...@hixie.ch wrote:
Like most widgets, I think the answer is Web Components.
As far as I can tell styling form controls is an unsolved problem and
Components does not seem to be tackling it. We always play the
Components card (and before that the XBL
http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#tables
says:
# The table element's width attribute maps to the dimension
# property 'width' on the table element.
...
# The td and th elements' width attributes map to the dimension
# property 'width' on the
On Wed, 2 Jan 2013, Anne van Kesteren wrote:
On Wed, Jan 2, 2013 at 8:53 PM, Ian Hickson i...@hixie.ch wrote:
Like most widgets, I think the answer is Web Components.
As far as I can tell styling form controls is an unsolved problem and
Components does not seem to be tackling it. We always
On 1/2/13 4:37 PM, Ian Hickson wrote:
Wait, Web Components isn't solving this? I thought this was one of the
main use cases of Web Components.
As far as I can tell, Web Components is doing the following:
1) Defining a way for authors to implement custom widgets.
2) Defining a way to maybe
On 1/3/2013 4:35 AM, Anne van Kesteren wrote:
On Wed, Jan 2, 2013 at 8:53 PM, Ian Hickson i...@hixie.ch wrote:
Like most widgets, I think the answer is Web Components.
As far as I can tell styling form controls is an unsolved problem and
Components does not seem to be tackling it. We always
On Wed, 2 Jan 2013, Boris Zbarsky wrote:
On 1/2/13 4:37 PM, Ian Hickson wrote:
Wait, Web Components isn't solving this? I thought this was one of the
main use cases of Web Components.
[...] and it is certainly not doing:
4) Defining the browser-defined custom widgets using the
On 1/3/13 12:10 AM, Ian Hickson wrote:
On Wed, 2 Jan 2013, Boris Zbarsky wrote:
On 1/2/13 4:37 PM, Ian Hickson wrote:
Wait, Web Components isn't solving this? I thought this was one of the
main use cases of Web Components.
[...] and it is certainly not doing:
4) Defining the
14 matches
Mail list logo
