the JS program immediately.
(Validator.nu also advertises Accept-Encoding: gzip via OPTIONS, but
I'm not aware of any client automatically picking it up from there.)
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
trimming is
specified, implementors don't always do it. My conclusion is that it's
better to specify that keyword attribute values are compared without
trimming. (Unless, of course, the attribute in question takes a
whitespace-separated list of tokens.)
--
Henri Sivonen
[EMAIL PROTECTED]
http
between an
ancestor svg element and the selector subject would be good enough.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
is defined by RFC 3236. As implemented, the
media type isn't restricted to a particular point version of XHTML and
browsers don't implement 1.1.
(In fact, the media types in the table aren't defined by the specs in
the Defined by column in general, but are defined by RFCs.)
--
Henri Sivonen
omit it,
and it isn't much uglier than an XML signature file on the top level
of the zip archive.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Apr 14, 2009, at 11:57, Thomas Roessler wrote:
On 14 Apr 2009, at 10:27, Henri Sivonen wrote:
Wouldn't it be simpler to use jar signing instead of inventing a
new way of signing zip files with implementation dependencies on
XML signatures and spec dependencies on XSD? (Why does the spec
On Apr 14, 2009, at 13:01, Thomas Roessler wrote:
On 14 Apr 2009, at 11:42, Henri Sivonen wrote:
XSD datatypes are too vague, allow whitespace where the spec writer
didn't mean to allow whitespace or allow surprising values (like
0 and 1 when the spec writer though (s)he'd be allowing
the traditional way,
you are a step away from using jar-compatible manifests. :-) This
would address issue #3.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Apr 15, 2009, at 15:00, Marcos Caceres wrote:
On Tue, Apr 14, 2009 at 4:19 PM, Henri Sivonen hsivo...@iki.fi
wrote:
On Apr 14, 2009, at 14:38, Marcos Caceres wrote:
I think it would be more productive to help us address the issues
that you
mentioned, instead of asking us to dump
?)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
was to isolate even different instances
of the same widget.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
feature name string of the specifiers of the feature itself just meant
it to be available to Web content unconditionally and didn't bother to
mint a widget feature string?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
that
the security aspect requires an authorization and doesn't make sense
if the dangerous feature are simply imported silently.) As far as I
can tell, the spec doesn't currently explain what the UA is supposed
to do with the 'feature list' once built.
--
Henri Sivonen
hsivo...@iki.fi
http
the definition of what a feature is includes a video
codec in addition to APIs. Does BONDI expect video codecs to be
sensitive to security policies? Do you envision undeclared video
codecs to be withheld from the HTML5 source fallback and
canPlayType()?
--
Henri Sivonen
hsivo...@iki.fi
http
On Jun 2, 2009, at 16:02, Robin Berjon wrote:
On Jun 2, 2009, at 14:57 , Henri Sivonen wrote:
Please include a corresponding UA requirement to obtain
authorization from the user for the features imported with
feature. (It seems that the security aspect requires an
authorization
somewhere.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Jul 2, 2009, at 12:11, Giovanni Campagna wrote:
2009/7/2 Cameron McCormack c...@mcc.id.au:
Henri Sivonen:
Gecko bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=500937
The proposed patch there and (based on black-box testing) WebKit
solve
the issue by running the HTML serialization
. Instead, it has to have two (the natural choice flowing from XML specs)
or the IDness of attributes has to depend on the presence of other attributes
(the choice taken by SVG 1.2 Tiny).
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
interoperate with Web browsers.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
active at
the notification time.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
advanced (for
example, embed webkit to display fully functional notifications)?
It's not a given that it's an advancement in user experience terms not to force
all ambient notifications into a consistent form.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
very often. I don't recall ever
seeing a signed Firefox extension or a signed Eclipse plug-in.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
element node even after walking the parent chain, the
context passed to the HTML fragment parsing algorithm should be body in the
XHTML namespace. I don't know DOM Range well enough to say how this situation
can arise.)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
, so the
script behaves like a script created with document.createElement(script) when
inserted into a document.
I'd be interested in use cases around createContextualFragment in order to get
a better idea of which behavior should be the correct behavior going forward.
--
Henri Sivonen
hsivo
? I assume that typically one would use
overrideMimeType() when knowing ahead of time that the config of the
server responding to XHR is bogus.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
Adding [XHR2] to the subject to comply with the instructions. Sorry
about the noise.
On Tue, 2011-04-19 at 12:04 +0300, Henri Sivonen wrote:
In reference to
http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#dom-xmlhttprequest-overridemimetype
It seems to me that XHR2 allows overrideMimeType
without a new HTML element:
https://github.com/mozilla/openwebapps/blob/master/docs/ACTIVITIES.md
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
and
responseText is already used with text/html.
As it stands, the XHR2 spec defers to a part of HTML that has
legacy-oriented optional features. It seems that it makes sense to
clamp down those options for XHR.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
machinery of an app, it's much harder to figure out what part of the
system the problem should be attributed to.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Fri, Sep 23, 2011 at 11:26 AM, Henri Sivonen hsivo...@iki.fi wrote:
Applying all the legacy text/html craziness
Furthermore, applying full legacy text/html craziness involves parser
restarts for GET requests. With a browsing context, that means
renavigation, but I really don't want to support
On Mon, Sep 26, 2011 at 12:46 PM, Jonas Sicking jo...@sicking.cc wrote:
On Fri, Sep 23, 2011 at 1:26 AM, Henri Sivonen hsivo...@iki.fi wrote:
On Thu, Sep 22, 2011 at 9:54 PM, Jonas Sicking jo...@sicking.cc wrote:
I agree that there are no legacy requirements on XHR here, however I
don't think
was loaded from after the fact, so debugging doesn't seem any
harder.
If that counts as not harder, I concede this point.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
in Gecko when there's no declaration.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
to continue working.
* responseXML considers meta in a deterministic way (no timer for
bailing out before 1024 bytes if the network stalls).
Which property do we give up?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
is much less extreme than the more
enlightened position e.g. HTML5 App Cache manifests take: Requiring
everyone to use UTF-8 for a new feature so that declarations aren't
needed.)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
responseXML for text/html.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Fri, Sep 30, 2011 at 3:35 PM, Anne van Kesteren ann...@opera.com wrote:
On Fri, 30 Sep 2011 14:29:32 +0200, Henri Sivonen hsivo...@iki.fi wrote:
On Fri, Sep 30, 2011 at 3:04 PM, Anne van Kesteren ann...@opera.com
wrote:
I do not see why text and moz-chunked-text have to be the same
into a CSS OM.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
the opportunity to make
a new feature less crazy.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
for tags other than tr appearing as the outermost tag?
What would you expect the my examples above to do and why?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
does.
Stuff to debate includes what to do about Content MathML, what to do
about object elements that appear to reference SVG and what to do
about embed elements that bear Microdata attributes.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
parsing. No need
to first get responseText and then pass it to something else.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
their mind now, but we shouldn't
let them flipflop now that we've reached interop.
This ship has sailed.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
doing something different would be bad.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
;
will just drop the div on the floor.
By what mechanism? (It didn't implement and run Yehuda's suggestion,
but I'm pretty sure it wouldn't drop the div. Why would we put
additional effort into dropping the div?)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Fri, Nov 11, 2011 at 1:42 PM, Henri Sivonen hsivo...@iki.fi wrote:
As a bonus, developers would need to call createDocumentFragement() first.
Doh. Would *not* need to call createDocumentFragement() first.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
type for the purpose of character
encoding.
* Making XHR not support HTML parsing in the synchronous mode.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
the description of what
needs to be implemented in order to successfully render the Web.
By all means put some kind of Surgeon General's warning about race
conditions on localStorage but, please, let's not hide the description
of the feature from specs.
--
Henri Sivonen
hsivo...@iki.fi
http
On Wed, Nov 16, 2011 at 12:40 PM, Henri Sivonen hsivo...@iki.fi wrote:
* Making XHR not support HTML parsing in the synchronous mode.
In reference to the other thread about discouraging synchronous XHR
(outside Workers), this change ended up being made in Gecko. (HTML
parsing in XHR still
features. Otherwise,
there's a risk of getting sucked into implementing bad optional
features anyway.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Mon, Nov 21, 2011 at 8:26 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Nov 16, 2011 at 2:40 AM, Henri Sivonen hsivo...@iki.fi wrote:
* For text/html responses for response type and document, the
character encoding is established by taking the first match from this
list in this order
for interpreting existing XPath 1.0 queries, but
it seems like a bad idea to build on a spec whose authors have put
compatibility into a side mode and what's considered the main thing
isn't fully compatible with existing queries.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
sense to spec what
they already support instead inventing a new API.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
want to use XSLT2 in browsers to license Saxon-CE (XSLT2
implemented in JavaScript) from Saxonica instead of expecting native
implementations in browsers.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
have the advantage that they wildcard the namespace by
default, so it's feasible to define APIs that don't even have
namespace binding mechanisms.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
as an interchange
encoding beyond writing evil test cases. Defining it as a valid
encoding is reprehensible.
Does anyone actually transfer JSON as UTF-16?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
implementations in
the future, I think we shouldn't expose responseText for JSON.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
parser
in our first iteration of implementing the json responseType.
FWIW, Gecko parses XML and HTML in a streaming way as data arrives
from the network. When readyState changes to DONE, the document has
already been parsed.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
proliferating obsolete stuff is harmful.
Which laws or regulations require compliance with some of the
above-mentioned specs? Have bugs been filed on those laws and
regulations?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
converged on the spec worry me,
though. I'm still hoping for a design that doesn't require parser
changes at all and that doesn't blow up in legacy browsers (even
better if the results in legacy browsers were sane enough to serve as
input for a polyfill).
--
Henri Sivonen
hsivo...@iki.fi
http
/html5/rdfa/). Proof structure and semantics can overlay
the HTML5 and/or the RDFA can relate elements to referenced external
resources.
What kind of software do expect to consume of this kind of data?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
(template ancestor or
DocumentFragment marked as inert as an ancestor). It's unclear to me
what the performance impact will be.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
as various XML experiences from non-browser contexts.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
.
If the API required the caller to request SVG explicitly, would it be
a sure thing that jQuery would build magic heuristics on the library
side?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
to parse and returns the resulting
DocumentFragment, e.g. document.parse(string) to keep it short.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
flag of the
document and returns a DocumentFragment (or has an optional extra
argument for forcing XML parsing explicitly).
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
its behavior.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
considerations of
consistent behavior across already-deployed browsers (including IE9,
soon IE10 and the Android stock browser) and future browsers.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
believe that this template contents should be children of
the template element in the DOM instead of being behind a special
wormhole to another document while parsing and serializing as if the
special wormhole wasn't there.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
.
Even though it'll technically work, it might look ugly due to scaling.
Shouldn't it be up to the user to refrain from using ugly apps instead
of the developer preventing them?
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
on IRC were confused, because I mistook the
Worker-specific API for the API proposed for the main thread.)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
persists.
The reason why I care about correcting recounts of past SVG working
group opinion on this topic is that I think it's better for learning
from mistakes if the learning is based on the truth of what happened.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
serialization should be considered huge red flags indicating faulty
design.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
for
all sorts of arguments that we can make the parser generate whatever
data structures regardless of what the input looks like and we'll end
up in a world of pain. It's bad enough that isindex is a parser macro.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
and the new
property that leads to a fragment that belongs to a different owner
document.
(My non-objection to creating normal children in the DOM should not be
read as a commitment to support templates Gecko.)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
On Tue, Jun 12, 2012 at 12:14 AM, Rafael Weinstein rafa...@google.com wrote:
On Mon, Jun 11, 2012 at 3:13 PM, Henri Sivonen hsivo...@iki.fi wrote:
On Thu, Jun 7, 2012 at 8:35 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Just saying that querySelector/All doesn't match elements in a
template
would want.
That's not really a problem as long as subtrees with elements in the
template namespaces are rooted at a display: none; template element.
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
to make the bet?)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
legacy code to the Web using the default settings of
Firefox, so I'm hoping to remove the big chunk of legacy code instead
of fixing it properly.)
--
Henri Sivonen
hsivo...@iki.fi
http://hsivonen.iki.fi/
that desugars into NavigationController into the same
manifest? Are we absolutely sure that we don't want the manifest to
grow to do AppCache-ish things that pretty much require the
declaration to be an attribute on html?
--
Henri Sivonen
hsivo...@hsivonen.fi
http://hsivonen.fi/
80 matches
Mail list logo
