g"
because the registration for it was removed) and non-redundant.
Best wishes,
Brett
On 6/10/2014 2:00 PM, Dominic Cooney wrote:
On Mon, Jun 9, 2014 at 4:00 PM, Brett Zamir <mailto:bret...@gmail.com>> wrote:
I was looking to make a genuine polyfill for (not just a
shim), and I f
I was looking to make a genuine polyfill for (not just a shim),
and I found Polymer's CustomElements helpful, but realized too late that
the spec required "x-" prefixes.
I still feel like it would be useful to have a means for polyfills to be
built according to well-recognized semantics via a
I am wondering whether thought has been given to allowing selectors
beginning with ">" for use with querySelector/All such as:
" > .sharedClass"
Sometimes one wishes to resolve a precise hierarchy but relative to the
current element. Currently, to do so with precision, one must either
spe
user to parse the response text, why not simply allow each event to be a
JSON-encoded object of some kind (boolean, number, string, array,
object). Then the event.data could be an object which was already
conveniently accessible to JavaScript consumers. Presumably server-side
libraries would ha
I am a newcomer to the Server-Sent Events spec, so my apologies if I am
covering old ground.
While I can understand that Server-Sent Events may be intending to start
off simple, I wonder whether there is some reason a formal mechanism was
not adopted to at least allow the specification of even
On 6/29/10 2:36 PM, Chris Wilson wrote:
See, this is exactly why we asked the question - because it seems
that behavior is inconsistent, we're not sure what the expectation is.
Note that the Firefox behavior I described is irrelevant to
specification efforts, because it's not visible to web pa
On 6/25/2010 5:09 PM, Anne van Kesteren wrote:
On Wed, 23 Jun 2010 01:53:51 +0200, Travis Leithead
wrote:
This topic came up internally on the IE team, and we thought it would
be noteworthy to put this question before the working groups in hopes
of getting a spec clarification made.
The ques
