"webstats" gathered but for your
dataset that would be great. But anything really might give some insight
into what is going on on the Web. :-)
--
Anne van Kesteren
http://annevankesteren.nl/
.
David Baron came up with the current design.
--
Anne van Kesteren
http://annevankesteren.nl/
n no less!), which
indicates a certain preference, but again it's not clear whether this
can be regarded as authoritative.
Any input?
Both are fine.
PS: Yes, that was a horrible pun.
Heh, I missed it initially.
--
Anne van Kesteren
http://annevankesteren.nl/
anyone else have an opinion on this?
I think the main concern back then was compatibility with legacy browsers.
I would not mind easing the restriction as relatively soon all browsers
will have HTML5 comment parsing. And given that are clear
delimiters disallowing -- does not
, but that is always the case as they
want to preserve whitespace details, etc., too. At least editors that have
both a text and visual interface.
--
Anne van Kesteren
http://annevankesteren.nl/
robably want to use a direct API, we wouldn't want to have scripts
have to poke at the DOM in real time.
For the "Google suggest"-style UI you also need to be able to show more
than just options. Google has buttons, tables, images, and all kinds of
other things in its dropdown
On Sun, 19 Dec 2010 08:42:09 +0100, Henry Chan
wrote:
*bump*
This is really serious, it blocks a very good use of the API, and it's
unreliable to use it if back and forward is clicekd before onload.
This got fixed, no?
http://html5.org/tools/web-apps-tracker?from=5685&to=5686
--
ected to the current APIs as wired
alternatives do. I think Don meant to be able to scan other types of
devices and be able to interact with them.
What makes other devices so different that they need special exposition?
They are far more common. We always try to optimize the common case.
--
Ann
cases? Not sure if it is really worth it
though.
--
Anne van Kesteren
http://annevankesteren.nl/
web pages would be quite the security risk.
- talk to the device with some kind of stream/socket
Does anyone think this could be a good idea?
I certainly think it's cool. :-)
--
Anne van Kesteren
http://annevankesteren.nl/
ay what its use is.
That is only interesting for devices that are commonly used. For the long
tail you need some kind of open-ended API.
--
Anne van Kesteren
http://annevankesteren.nl/
tc. can be connected in a
browser-agnostic way (i.e. no extensions) and the page could provide the
implementation. Seems somewhat far away though. :-)
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 02 Dec 2010 14:10:33 +0100, Anne van Kesteren
wrote:
For fetching EventSource resources treating mailto as if it was a 204
does not work as that reestablishes the connection. The result should be
more akin a network error of some kind I think. Similarly to how other
cross-origin
is actually ever used for this. (Did not put time in
investigating that for now.)
--
Anne van Kesteren
http://annevankesteren.nl/
this.
--
Anne van Kesteren
http://annevankesteren.nl/
onger than the equivalent javascript:
URI. Again, one would have to find non-silly use cases here.
mandelbrot sets
These can also be done with data:text/html,... and maybe
. It is slightly longer, but not much.
--
Anne van Kesteren
http://annevankesteren.nl/
via
Bluetooth? Should we really have a USB/Bluetooh/Firewire/etc. distinction
at the web platform level? That seems like a bad thing.
--
Anne van Kesteren
http://annevankesteren.nl/
some more vendors, etc. But over
the years there have not been many extensions at all so this is all rather
manageable.)
--
Anne van Kesteren
http://annevankesteren.nl/
wrong, but another approach I don't know.
http://dev.w3.org/csswg/cssom-view/#extensions-to-the-range-interface
--
Anne van Kesteren
http://annevankesteren.nl/
appropriate than the one described here.
Do you have tests for this by any chance? I agree it makes sense to always
treat them as a group.
--
Anne van Kesteren
http://annevankesteren.nl/
drive via and
thus it will be up to the application to ensure that whatever is sent to
the other peer is usable there.
That is quite a different scenario from exchanging a live media feed.
--
Anne van Kesteren
http://annevankesteren.nl/
same browser (or select from a restricted
group of browsers only) for a live communication. I guess it's
workable, but kinda strange for an open platform like the Web.
I would not really even want to consider that as an acceptable outcome, to
be honest.
--
Anne van Kesteren
data, and
-two "data:" lines followed by an empty line should fire a message
event with an LF as data
(push every line followed by an LF, then remove the last LF and fire it)
That works for me. Hixie? People from WebKit?
--
Anne van Kesteren
http://annevankesteren.nl/
nt" keyword, so that instead of rgba(0,0,0,0)
it means A=0 with the mean RGB of the adjacent colour stops. That
would let it work as people naturally expect when they use that
keyword, and they can use the rgba() syntax if they really want
transparent black or transparent yellow or transparent red etc.)
The people at Opera responsible for the graphics layer agree with Philip's
point of view. They also pointed out we do support rgba() in SVG.
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 14 Oct 2010 14:23:41 +0200, ATSUSHI TAKAYAMA
wrote:
On Wed, Oct 13, 2010 at 10:00 AM, Anne van Kesteren
wrote:
On Tue, 12 Oct 2010 06:41:59 +0200, ATSUSHI TAKAYAMA
wrote:
It's a minor error in the spec in the Server-Sent Events spec.
http://dev.w3.org/html5/eventsource/#
he source code for the tests here:
http://tc.labs.opera.com/svn
If you want to contribute more tests following this style. Let me know!
--
Anne van Kesteren
http://annevankesteren.nl/
that the class changed, when no other
systems agree.
Well yes, obviously .class notation, #id, etc. would all have to remain
functioning. To me it makes sense to define ID/class-ness at the DOM
level. CSS operates on that level too.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 23 Nov 2010 20:06:02 +0100, Boris Zbarsky wrote:
On 11/23/10 2:02 PM, Anne van Kesteren wrote:
So if I set Element.className on an element that is not in a namespace
and has no attributes. Its attributes collection remains empty or
something?
Hmm. I would think this should throw
On Tue, 23 Nov 2010 19:48:03 +0100, Boris Zbarsky wrote:
On 11/23/10 12:58 PM, Anne van Kesteren wrote:
So that you do not need namespace knowledge.
Namespace knowledge where? As an implementor? Or as an author?
Either?
The whole point if a universal .classList and .className is to
ng/setting that property. Presumably XML grammars would use the
rules
at http://dev.w3.org/html5/spec/apis-in-html-documents.html#innerhtml
http://html5.org/specs/dom-parsing.html
It's simply called Element.innerHTML.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 23 Nov 2010 18:37:51 +0100, Boris Zbarsky wrote:
On 11/23/10 12:20 PM, Anne van Kesteren wrote:
My plan is to define Element.id, Element.className, Element.classList,
and getElementsByClassName in DOM Core. And tie getElementById to
Element.id somehow, tie Element.id to an attribute
.
--
Anne van Kesteren
http://annevankesteren.nl/
assName
to an attribute named "class".
--
Anne van Kesteren
http://annevankesteren.nl/
r why the TR/ version does not include a link there. TR/ is almost
always out of date.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 23 Nov 2010 11:52:12 +0100, John Knottenbelt
wrote:
Can anybody hazard a guess as to when the DOM Level 3 TR might be
updated with this change?
DOMTimeStamp is now defined in Web IDL. DOM Core is now
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html
--
Anne van Kesteren
d its dirty value flag is true, and the code-point length of the
element's value is greater than the element's maximum allowed value
length, then the element is suffering from being too long."
The "dirty value flag" is only true when the user has edited the control.
--
Anne van Kesteren
http://annevankesteren.nl/
e that the
mixed content warning event was fired. These issues have to be
investigated manually in any case.
Maybe this is something that should be warned for in the error console
instead then? Why does this need to be an API exposed to the web?
--
Anne van Kesteren
http://annevankesteren.nl/
.
The width/height IDL attributes are quite special. So those do not
exactly match I think. The ones for probably need some rewording
now they are no longer strings.
--
Anne van Kesteren
http://annevankesteren.nl/
se of a chatty file manager, or if
anyone has any ideas on how to mitigate this risk.
It should probably work with a whitelist.
--
Anne van Kesteren
http://annevankesteren.nl/
o, 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/
On Fri, 22 Oct 2010 23:09:41 +0200, Jonas Sicking wrote:
On Fri, Oct 22, 2010 at 2:57 AM, Anne van Kesteren
wrote:
I do not really get why it being comma-separated is not just the
submission format. The UI could be quite different. E.g. on the iPhone
email client it is more like an inline
Zbarsky, Boris"
a valid "email address"?
Not per HTML5.
--
Anne van Kesteren
http://annevankesteren.nl/
better to simply omit that trailing comma. Which
should be allowed. If the specification currently does not allow that
(somehow) it would be a bug and is just something that needs clarification.
--
Anne van Kesteren
http://annevankesteren.nl/
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/
p 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://annevankesteren.nl/
et 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 Kesteren
be this ought to be reworded
some. But then DOM Events is not done yet so...
3) Assuming I've understood the current spec correctly, what is
the use case for named events?
To make dispatching to different parts of the code easier. Without having
to create some kind of logic th
On Thu, 14 Oct 2010 15:46:30 +0200, Olli Pettay
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://annevankesteren.nl/
t think this is an error. (Although admittedly I once
thought it was.)
--
Anne van Kesteren
http://annevankesteren.nl/
s/Public/public-html-comments/2010Sep/0022.html
:-)
--
Anne van Kesteren
http://annevankesteren.nl/
non-empty paragraph.
Sites unfortunately do things like that so we cannot introduce this as a
global syntax.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 22 Sep 2010 23:49:53 +0200, Daniel Buchner
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/
e. I think the Gecko behavior makes
sense. Philip, can your test suite cover this?
--
Anne van Kesteren
http://annevankesteren.nl/
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/
hould 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 va
, in my opinion.
--
Anne van Kesteren
http://annevankesteren.nl/
bably 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/
event named readystatechange". The definition of "firing a simple
event named e" says to use the Event interface.
--
Anne van Kesteren
http://annevankesteren.nl/
. That about:srcdoc does not resolve does not mean its browsing
context cannot be navigated.
--
Anne van Kesteren
http://annevankesteren.nl/
cript, 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/
ozilla.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/
ArrayBuffer
is the way of the future?
--
Anne van Kesteren
http://annevankesteren.nl/
nd experimental attributes should really be avoided and only be
around for limited amount of time...
--
Anne van Kesteren
http://annevankesteren.nl/
her is that when you 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/
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/
Thanks for the changes, some comments below.
On Tue, 31 Aug 2010 01:58:52 +0200, Ian Hickson 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 o
, 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/
On Sun, 29 Aug 2010 15:01:27 +0200, L. David Baron
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 matching beyond
, seems like a good idea.
--
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
llowed in XHTML.
--
Anne van Kesteren
http://annevankesteren.nl/
= '&%;'
inside it would be expanded the moment innerHTML is invoked
</tt><tt>(inside script entities are not expanded) and thus be safe from
</tt><tt>"" injection and such. So yes, it happens after.
--
Anne van Kesteren
http://annevankesteren.nl/
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/
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 wrote:
On Thu, 29 Jul 2010, Anne van Kesteren wrote:
On Wed, 28 Jul 2010 01:32:13 +0200, Ian Hickson wrote:
> I've been working under the assumption that we want to eradicate as
> many differences between XHTML and HTML as possibl
ibute 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/
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/
some sorts. And if that should happen, should
the sandbox="" attribute disable it?
Cheers,
--
Anne van Kesteren
http://annevankesteren.nl/
e name. 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/
.
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/
On Mon, 16 Aug 2010 11:23:55 +0200, Maciej Stachowiak
wrote:
We do consider this, but since the status quo is "every browser but
Firefox implements it", it's not clear that flipping WebKit-based
browsers from one column to the other is a genuine interoperability
improvement. Nor does it se
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
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 MANIFEST"
://whatwg.org/C available for people with slow connections/browsers.
--
Anne van Kesteren
http://annevankesteren.nl/
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://annevankesteren.nl/
parsers.
Per the parser section there is only one. See the end of
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#parsing-0
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 11 Aug 2010 13:35:30 +0200, Silvia Pfeiffer
wrote:
On Wed, Aug 11, 2010 at 7:31 PM, Anne van Kesteren
wrote:
While players are transitioning to WebSRT they will ensure that they do
not break with future versions of the format.
That's impossible, since we do not know what f
On Wed, 11 Aug 2010 10:30:23 +0200, Silvia Pfeiffer
wrote:
On Wed, Aug 11, 2010 at 5:04 PM, Anne van Kesteren
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 (or
need for a replacement) has not
at all and everyone else supports most of the
extensions the WebSRT format has.
--
Anne van Kesteren
http://annevankesteren.nl/
ike a huge loss.)
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,
-
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://annevankesteren.nl/
mplex 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/
hould 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.
der W3C drafts or in
subversion, e.g.
http://www.w3.org/TR/2009/WD-html5-20090212/video.html#cue-ranges
Also -- is trackgroup out of the spec?
It was never in, as far as I know. :-)
--
Anne van Kesteren
http://annevankesteren.nl/
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://annevankesteren.nl/
as a concern we would not be having this discussion.
--
Anne van Kesteren
http://annevankesteren.nl/
part of the reason
why we have in the first place.
--
Anne van Kesteren
http://annevankesteren.nl/
id 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/
rough.
--
Anne van Kesteren
http://annevankesteren.nl/
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/
801 - 900 of 1841 matches
Mail list logo
