http://mathias.html5.org/specs/javascript/#escaped-reserved-words says:
JavaScript implementations must support ECMAScript identifiers that unescape
to a reserved word, as long as at least one character is escaped using a
Unicode escape sequence.
For example, var var; throws a syntax error,
Hi,
Currently, there are only two ways to invoke the clear regions that
cover the pixels algorithm: by calling either addHitRegion() or
clearRect(). Authors should be able to explicitly remove a hit region as
well, with a removeHitRegion(id) method.
Consider a region of a canvas which the author
There's also just removing the element from the DOM. Yes, I'd like a
removeHitRegion(Element) feature; though I can skate by with the empty
addHitRegion method.
I've not seen a response from you regarding the issues that Richard and Steve
have brought up around the lightweight nodes
Hi,
As things currently stand in the spec, implementations basically need to
keep N+1 bitmaps per canvas, where N is the number of hit regions. I
doubt any implementors would be enthusiastic to implement hit regions
like this. From a WebKit perspective, we'd much prefer keeping a Path
for each
On Jul 5, 2012, at 1:05 PM, Edward O'Connor eocon...@apple.com wrote:
Hi,
As things currently stand in the spec, implementations basically need to
keep N+1 bitmaps per canvas, where N is the number of hit regions. I
doubt any implementors would be enthusiastic to implement hit regions
On Thu, 5 Jul 2012, Edward O'Connor wrote:
As things currently stand in the spec, implementations basically need to
keep N+1 bitmaps per canvas, where N is the number of hit regions. I
doubt any implementors would be enthusiastic to implement hit regions
like this. From a WebKit
On Fri, Jun 29, 2012 at 4:24 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 21 Feb 2012, Glenn Maynard wrote:
I don't think the existence of implicit submit should depend on platform
conventions, though, for interop on forms without visible submit
buttons. The form implicit submit takes
On Jul 5, 2012, at 2:25 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 5 Jul 2012, Edward O'Connor wrote:
As things currently stand in the spec, implementations basically need to
keep N+1 bitmaps per canvas, where N is the number of hit regions. I
doubt any implementors would be
On Thu, 5 Jul 2012, Simon Fraser wrote:
On Jul 5, 2012, at 2:25 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 5 Jul 2012, Edward O'Connor wrote:
As things currently stand in the spec, implementations basically need
to keep N+1 bitmaps per canvas, where N is the number of hit regions.
On Jul 5, 2012, at 10:06 PM, Ian Hickson i...@hixie.ch wrote:
I think its up to the author to manage their set of paths appropriately,
independently from the drawing operations.
Having the drawing mechanism work in a tightly integrated fashion with the
region code IMHO helps authors avoid
10 matches
Mail list logo
