of email addresses too, either as another @type
value, or using some opt-in boolean attribute.
Yeah, it was supported in the past I think. I forgot why support was
dropped.
--
Anne van Kesteren
http://annevankesteren.nl/
policy. Are there any plans to formally include CORS in the spec?
Yes. As soon as CORS for XMLHttpRequest is more widely deployed we'll
start to introduce it elsewhere in the platform.
--
Anne van Kesteren
http://annevankesteren.nl/
with event.type set to the custom event name.
Well, it dispatches an event that uses the MessageEvent interface. But
e.g. a function attached to onmessage will not be invoked, as the event is
not named message, but something else. So you need
obj.addEventListener(customEvent, ...).
--
Anne van
and the returned string would contain the file system path.
It seems wrong to expose it in a way native to a particular operating
system so it seems better to filter it out for now even if that is more
work. We should keep web platform APIs OS-independent.
--
Anne van Kesteren
http
On Thu, 14 Oct 2010 15:46:30 +0200, Olli Pettay olli.pet...@helsinki.fi
wrote:
may I wonder why on earth any new API, like
link.sizes uses PutForwards?
IMHO, PutForwards should be limited to the
awkward DOM0 APIs like window.location.
What's wrong with PutForwards?
--
Anne van Kesteren
http
.
--
Anne van Kesteren
http://annevankesteren.nl/
. (Although admittedly I once
thought it was.)
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 22 Sep 2010 23:49:53 +0200, Daniel Buchner dan...@mozilla.com
wrote:
Thoughts?
I think CSSColorComponentValue in the CSSOM should eventually get this
ability. Discussion on CSSOM take mostly place on www-st...@w3.org.
--
Anne van Kesteren
http://annevankesteren.nl/
code. I think the Gecko behavior makes
sense. Philip, can your test suite cover this?
--
Anne van Kesteren
http://annevankesteren.nl/
parameter).
Yeah, I was wondering why that was not acceptable here. (Using /script?v=1
etc. where /script?v=x has near-infinite caching.)
--
Anne van Kesteren
http://annevankesteren.nl/
.
There should be a more thought out API for multipart/form-data since we
have the new FileApi.
Of course:
http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#the-formdata-interface
Any suggestions? (Or, any knowledge how it is done today? I can't find
anything about it! Crazy.)
--
Anne van
probably recommend against them for the
next couple of years though, as only browsers would support that feature
in the immediate future.
--
Anne van Kesteren
http://annevankesteren.nl/
to transmit bytes, in my opinion.
--
Anne van Kesteren
http://annevankesteren.nl/
a
simple event named readystatechange. The definition of firing a simple
event named e says to use the Event interface.
--
Anne van Kesteren
http://annevankesteren.nl/
of the empty
string. That about:srcdoc does not resolve does not mean its browsing
context cannot be navigated.
--
Anne van Kesteren
http://annevankesteren.nl/
. are we sure ArrayBuffer
is the way of the future?
--
Anne van Kesteren
http://annevankesteren.nl/
://wiki.mozilla.org/Security/CSP/AllowedScripts
It prevents a bunch of things, but when loaded in an iframe someone else
on the same-origin can still inject a script of some sorts.
--
Anne van Kesteren
http://annevankesteren.nl/
executing script, then it's not trying to withhold any
privileges.
Fair enough. I guess if one page gets compromised all else that is same
origin is lost anyway.
--
Anne van Kesteren
http://annevankesteren.nl/
that are
associated with the cache containing those resources.
Thanks. We currently have a same-origin restriction in place for explicit
entries, but will update to match the specification.
--
Anne van Kesteren
http://annevankesteren.nl/
save the video to disk the browser will fix up
the extension correctly, if needed.
If you sniff you can fix it up correctly too.
--
Anne van Kesteren
http://annevankesteren.nl/
. And experimental attributes should really be avoided and only be
around for limited amount of time...
--
Anne van Kesteren
http://annevankesteren.nl/
On Sun, 29 Aug 2010 15:01:27 +0200, L. David Baron dba...@dbaron.org
wrote:
On Wednesday 2010-08-25 10:28 +0200, Anne van Kesteren wrote:
We need a feature for case-insensitive matching in Selectors already
for XHTML (if we really care about this, not sure we do).
Allowing case-insensitive
to
text, too.
Or even more alternatively we could decide not to care about this being
difficult to select since in practice people will use lowercase values.
--
Anne van Kesteren
http://annevankesteren.nl/
Thanks for the changes, some comments below.
On Tue, 31 Aug 2010 01:58:52 +0200, Ian Hickson i...@hixie.ch wrote:
On Sat, 7 Aug 2010, Anne van Kesteren wrote:
2) Is there any reason we cannot also use this no browsing context
clause to define document.cookie rather than having a special type
as well?
Yeah, seems like a good idea.
--
Anne van Kesteren
http://annevankesteren.nl/
. not allowed in XHTML.
--
Anne van Kesteren
http://annevankesteren.nl/
With the current model makingyourinterwebsboring.com can define a cache
manifest and basically point to a lot of external news sites. When any of
those sites is then fetched directly they would be taken from the cache.
That does not seem optimal.
--
Anne van Kesteren
http
is the way to go.
Would Firefox / Safari support text/srt files in some undocumented fashion
then or just simply not support those? The former would not really be an
acceptable solution to me.
--
Anne van Kesteren
http://annevankesteren.nl/
ele.innerHTML = '%;'
inside script it would be expanded the moment innerHTML is invoked
(inside script entities are not expanded) and thus be safe from
/script injection and such. So yes, it happens after.
--
Anne van Kesteren
http://annevankesteren.nl/
.
We need a feature for case-insensitive matching in Selectors already for
XHTML (if we really care about this, not sure we do).
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 25 Aug 2010 01:00:50 +0200, Ian Hickson i...@hixie.ch wrote:
On Thu, 29 Jul 2010, Anne van Kesteren wrote:
On Wed, 28 Jul 2010 01:32:13 +0200, Ian Hickson i...@hixie.ch wrote:
I've been working under the assumption that we want to eradicate as
many differences between XHTML and HTML
of some sorts. And if that should happen, should
the sandbox= attribute disable it?
Cheers,
--
Anne van Kesteren
http://annevankesteren.nl/
).
I was talking about the events. They are synchronous in WebKit as far as I
can tell. I'm happy to define them as asynchronous though. Being
compatible with Gecko seems better.
--
Anne van Kesteren
http://annevankesteren.nl/
a trawl of the attribute index.
Yeah, see e.g. the various form* attributes, autofocus, item* attributes.
The only new attribute I can think of with a dash is data- and that's a
special case. Elements have no dashes at all.
--
Anne van Kesteren
http://annevankesteren.nl/
and paste -- as you
indicate -- that does make it more interesting to keep, in my opinion.
(What is up with Safari and the w() function on Live DOM Viewer by the
way? It very rarely works for me. Do I need to run nightlies?)
--
Anne van Kesteren
http://annevankesteren.nl/
to do with it. But e.g.
external hard drives are being considered and whether that goes over
Bluetooth or USB will hopefully be transparent to the API.
--
Anne van Kesteren
http://annevankesteren.nl/
. In fact, iirc we follow the policy that new attribute
names will not have hyphens in them, unless it is for some kind of pattern
(like data-).
--
Anne van Kesteren
http://annevankesteren.nl/
on legacy features when
we can. Even if it's only one feature at a time.
--
Anne van Kesteren
http://annevankesteren.nl/
On Fri, 13 Aug 2010 15:02:01 +0200, Patrick Mueller
pmue...@muellerware.org wrote:
On 8/12/10 6:29 PM, Ian Hickson wrote:
On Thu, 29 Jul 2010, Anne van Kesteren wrote:
XML would be much too complex for what is needed. We could possibly
remove the media type check and resort to using the CACHE
://whatwg.org/C available for people with slow connections/browsers.
--
Anne van Kesteren
http://annevankesteren.nl/
.
But it is not complex at all and everyone else supports most of the
extensions the WebSRT format has.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 11 Aug 2010 10:30:23 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 5:04 PM, Anne van Kesteren ann...@opera.com
wrote:
That is the approach we have for most formats (and APIs) on the web
(CSS, HTML, XMLHttpRequest) and so far a version identifier need
On Wed, 11 Aug 2010 13:35:30 +0200, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Wed, Aug 11, 2010 at 7:31 PM, Anne van Kesteren ann...@opera.com
wrote:
While players are transitioning to WebSRT they will ensure that they do
not break with future versions of the format.
That's
/current-work/multipage/video.html#parsing-0
--
Anne van Kesteren
http://annevankesteren.nl/
. Maybe we should make CORS easier
to use instead?
What exactly is hard about it?
(Though I should note we should carefully study whether using CORS here is
safe and sound. For instance, you may want to allow seamless embedding,
but not share content.)
--
Anne van Kesteren
http
.)
6) If you provide some hook or tell me how to do it I can define the
origin of the Document returned by responseXML in XMLHttpRequest.
If we can do all this that should turn it into a one-way dependency with
most definitions being completely self-contained.
Thanks,
--
Anne van
we use a string then -- a space-separated list of tokens? Constants
are somewhat icky to use in JavaScript and here you would have to use some
trickery if you would actually want to request several kinds of behaviors
using a single constant in the future.
--
Anne van Kesteren
http
should keep the differences, though, I'm
quite
happy to change the spec accordingly.
Do any other browser vendors have opinions here? Are there compatibility
constraints I'm not aware of?
I still think we should make matching on values always case-sensitive,
including in HTML.
--
Anne van
be much too complex for what is needed. We could possibly remove
the media type check and resort to using the CACHE MANIFEST identifier
(i.e. sniffing), but the HTTP gods will get angry.
--
Anne van Kesteren
http://annevankesteren.nl/
just more
complicated. But it does not become less complicated if you have your own
hosting environment either...)
But this discussion is premature. We should first have a couple of
implementations of seamless before we make things more complicated.
--
Anne van Kesteren
http
.
So if bandwidth was a concern we would not be having this discussion.
--
Anne van Kesteren
http://annevankesteren.nl/
of proprietary plugins -- is a large part of the reason
why we have video in the first place.
--
Anne van Kesteren
http://annevankesteren.nl/
problems with older user agents that incorrectly perceive
this as the end of a tag (tag close delimiter) when it appears in quoted
attribute values.
It is also disallowed by the HTML 4.01 Strict validator.
--
Anne van Kesteren
http://annevankesteren.nl/
iframe srcdoc=.../iframe which does what you propose with
the relatively small change that the sandboxed code is inside an attribute
rather than an element. For fallback the src attribute can be used.
--
Anne van Kesteren
http://annevankesteren.nl/
it: it didn't get through.
--
Anne van Kesteren
http://annevankesteren.nl/
manifest rather than creating some new kind of JSON-based format
that needs to be separately fetched.
--
Anne van Kesteren
http://annevankesteren.nl/
, and thereby potentially more vulnerable.
--
Anne van Kesteren
http://annevankesteren.nl/
have
already that gives a few extra features. At least that's what I make out
of the rough summary.
--
Anne van Kesteren
http://annevankesteren.nl/
be
leaving peer-to-messaging out... Streaming video via WebSocket is
something we definitely want to enable in due course, irrespective of
whether peer-to-peer messaging comes to fruition.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 19 May 2010 08:40:16 +0200, Shiki Okasaka sh...@google.com wrote:
On Tue, May 18, 2010 at 3:27 PM, Anne van Kesteren ann...@opera.com
wrote:
Can't they all just use org.w3c.dom? We cannot make the interface names
overlap anyway.
I think one module name for all of the Web platform
On Tue, 18 May 2010 10:52:53 +0200, Bjorn Bringert bring...@google.com
wrote:
On Tue, May 18, 2010 at 8:02 AM, Anne van Kesteren ann...@opera.com
wrote:
I wonder how it relates to the device proposal already in the draft.
In theory that supports microphone input too.
It would be possible
, scrolling through a document we're discussing, etc.
--
Anne van Kesteren
http://annevankesteren.nl/
there. But maybe I'm wrong and speech
input is a case that needs to be considered separately. It would still not
be like synchronous XMLHttpRequest though.
--
Anne van Kesteren
http://annevankesteren.nl/
are not part of the standard. Hopefully more
people will revisit this issue sometime soon.
Can't they all just use org.w3c.dom? We cannot make the interface names
overlap anyway.
--
Anne van Kesteren
http://annevankesteren.nl/
it.
I wonder how it relates to the device proposal already in the draft. In
theory that supports microphone input too.
--
Anne van Kesteren
http://annevankesteren.nl/
On Sat, 24 Apr 2010 17:58:10 +0200, Ojan Vafai o...@chromium.org wrote:
On Fri, Apr 23, 2010 at 8:41 PM, Anne van Kesteren ann...@opera.com
wrote:
On Fri, 23 Apr 2010 07:11:08 +0900, Ojan Vafai o...@chromium.org
wrote:
But there is already a default UI that lets you select a folder, a
file
application. However, for portability it would probably be better if these
were limited to fonts already on the Web.
--
Anne van Kesteren
http://annevankesteren.nl/
that forces us too as far as I can tell.
--
Anne van Kesteren
http://annevankesteren.nl/
van Kesteren
http://annevankesteren.nl/
On Sat, 01 May 2010 03:57:42 +0900, Eduard Pascual herenva...@gmail.com
wrote:
XHTML2's approach was clean and simple: section, h, and @role do
everything. Period.
Bullshit:
http://www.w3.org/TR/2006/WD-xhtml2-20060726/mod-structural.html#sec_8.5.
--
Anne van Kesteren
http
the problem of mixing h1-h6
with section/h. HTML5 did.
--
Anne van Kesteren
http://annevankesteren.nl/
would be required? It is designed to make this just
work so if anything is wrong I'd like to know. Specifically the resource
sharing check is what HTML would use here.
--
Anne van Kesteren
http://annevankesteren.nl/
requests (i.e. the requests
img makes).
Has Opera implemented cross domain origin-clean images?
Not yet.
--
Anne van Kesteren
http://annevankesteren.nl/
On Fri, 16 Apr 2010 16:54:12 +0900, Silvia Pfeiffer
silviapfeiff...@gmail.com wrote:
On Fri, Apr 16, 2010 at 5:03 PM, Anne van Kesteren ann...@opera.com
wrote:
It would simply always be UTF-8, much like text/cache-manifest and
text/event-stream.
There are plenty of SRT files out
of CSS support does.
CSS is by design, optional. I would hope a captioning format is not, since
captions are somewhat essential content information.
--
Anne van Kesteren
http://annevankesteren.nl/
functionality in something new. If we really want to
do SRT + HTML + CSS, then we should start completely from a blank
page.
It makes things easier for people familiar with authoring SRT. It also
makes it easier to change existing SRT files into rich SRT files.
--
Anne van Kesteren
http
important if I remember correctly. (More details can be found in the
public-h...@w3.org archives.)
--
Anne van Kesteren
http://annevankesteren.nl/
for details can be nothing more than:
details:not(open) :not(summary) {
display: none;
}
(Plus general default styling of details and summary, of course.)
That does not work well for text nodes. (Also, you meant [open], i.e.
including braces.)
--
Anne van Kesteren
http://annevankesteren.nl/
van Kesteren
http://annevankesteren.nl/
and introduce an ASCII case-insensitive flag for attribute value
selectors to deal with this issue.
--
Anne van Kesteren
http://annevankesteren.nl/
really a fallback position,
so it doesn't matter if we send null or throw an exception.
Isn't the fallback there to draw the img on a canvas and then extract
an ImageData object and pass that through to the worker?
--
Anne van Kesteren
http://annevankesteren.nl/
. Is it that
expectation that send(DOMString) can eventually send very different things
over the wire depending on how the server reacts to the initial handshake
request? How do the various options we have evaluate against the potential
scenarios coming out of that?
--
Anne van Kesteren
http
protocol overhead isn't reported.
Why? Progress events are completely different from this. This is about not
saturating the network with too much data; it makes sense if the actual
amount of data that is going to hit the network is known. (Yes, I changed
my mind.)
--
Anne van Kesteren
http
) would prefer this too. I.e. to not impose details of the
protocol on the API.
--
Anne van Kesteren
http://annevankesteren.nl/
.
--
Anne van Kesteren
http://annevankesteren.nl/
above, could a header be required on compliant browsers to
send a header along with their request indicating the originating
server's domain?
No, existing servers would still be vulnerable.
--
Anne van Kesteren
http://annevankesteren.nl/
they are
barred
from constraint validation ?
Seems to be a bug, unless the elements were intended to be in the category
listed.
--
Anne van Kesteren
http://annevankesteren.nl/
/
?
Servers are already free to obtain and mix in content from other sites,
so why can't client-side HTML JavaScript be similarly empowered?
Because you would also have access to e.g. IP-authenticated servers.
--
Anne van Kesteren
http://annevankesteren.nl/
to be correct: Firefox and Opera both just ignore the standard and get
this
wrong. Chrome just seems to get confused.
This changed a while ago due to compatibility problems. Consensus at the
time was to change DOM Core.
--
Anne van Kesteren
http://annevankesteren.nl/
(it changes the [[Prototype]] to be that it would have
been if the node had been created anew in the destination document).
--
Anne van Kesteren
http://annevankesteren.nl/
.
--
Anne van Kesteren
http://annevankesteren.nl/
for cookies then?
--
Anne van Kesteren
http://annevankesteren.nl/
from an
offscreen canvas to an onscreen one. Perhaps via a canvas ID.
postMessage() supports ImageData so you could use that.
--
Anne van Kesteren
http://annevankesteren.nl/
of
the input element?
You could e.g. style the border of the input element to show it has not
been used yet.
--
Anne van Kesteren
http://annevankesteren.nl/
do some trickery that their default style rule has higher
specificity than style= or some such to work around the issue WebKit ran
into.
--
Anne van Kesteren
http://annevankesteren.nl/
;-):
https://bugs.webkit.org/show_bug.cgi?id=21299
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 18 Feb 2010 23:06:12 +0100, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Feb 17, 2010 at 11:30 PM, Anne van Kesteren ann...@opera.com
wrote:
On Thu, 18 Feb 2010 00:15:25 +0100, Jonas Sicking jo...@sicking.cc
wrote:
So I suggest we add a method like
interface HTMLFormElement
with something else?
--
Anne van Kesteren
http://annevankesteren.nl/
working on XMLHttpRequest Level 2.
--
Anne van Kesteren
http://annevankesteren.nl/
anyway and at this experimental stage it is not
really clear whether your use case hits the 80/20 or is actually rather
uncommon and can be dealt with using a jQuery wrapper or some such.
--
Anne van Kesteren
http://annevankesteren.nl/
801 - 900 of 1655 matches
Mail list logo
