On Wed, 29 Jul 2009, Dean McNamee wrote:
For the curves, I don't really get the point of moveTo()ing to one of
the control points.
Me either, but at leave for quadratic and bezier curves, that seems to be
what browsers do.
--
Ian Hickson U+1047E
On Tue, Jul 28, 2009 at 4:07 AM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
On Tue, Jul 28, 2009 at 1:41 AM, Gregg Tavaresg...@google.com wrote:
It's ambiguous because images have a direction. An image that starts at
10
with a width of -5 is not the same as an
On Thu, 30 Jul 2009 02:49:01 +0200, Kartikaya Gupta lists.wha...@stakface.com
wrote:
It seems that most browsers do some sort of newline and tab removal from
URI attributes. For example, if you have
img src=foo
bar.jpg
browsers will still render the image called foobar.jpg despite the
On Thu, 30 Jul 2009 02:49:01 +0200, Kartikaya Gupta lists.wha...@stakface.com
wrote:
On a related note, I was wondering if all these spin-off specs could
be listed somewhere easy to find; it took me a while to locate the web
addresses one and I had to use google to find it. Putting a list
On Wed, Jul 29, 2009 at 7:38 PM, Nathan Hammondnat...@nathanhammond.com wrote:
Clarifications
1. window.history.pushState({}, Title,
/path/to/new/file.html?s=newvalue#newhash) replaces the current document
object with the one specified by the new URL. It then causes the event
popstate to fire
On Thu, 30 Jul 2009 08:49:12 +0200, Gregg Tavares g...@google.com wrote:
What are people's feelings on adding a Binary Archive API to HTML5?
I think it makes more sense to build functionality like this on top of the File
API rather than add more things into HTML5.
It seems like it would be
On Wed, Jul 29, 2009 at 5:49 PM, Kartikaya
Guptalists.wha...@stakface.com wrote:
It seems that most browsers do some sort of newline and tab removal from URI
attributes. For example, if you have
img src=foo
bar.jpg
browsers will still render the image called foobar.jpg despite the CRLF
I note in http://www.whatwg.org/specs/web-apps/current-work/#valid-date-string
that Dates before the year zero can't be represented as a datetime in
this version of HTML. This seems a serious omission. Why can we
represent the birth of Nero but not the birth of Julius Caesar? Are
there plans to
On Thu, Jul 30, 2009 at 2:37 PM, Elliotte Rusty
Haroldelh...@ibiblio.org wrote:
On Wed, Jul 29, 2009 at 5:49 PM, Kartikaya
Guptalists.wha...@stakface.com wrote:
It seems that most browsers do some sort of newline and tab removal from URI
attributes. For example, if you have
img src=foo
2009/7/30 Elliotte Rusty Harold elh...@ibiblio.org
I note in
http://www.whatwg.org/specs/web-apps/current-work/#valid-date-string
that Dates before the year zero can't be represented as a datetime in
this version of HTML. This seems a serious omission. Why can we
represent the birth of Nero
On Thu, 30 Jul 2009 15:05:10 +0100, Sam Kuper sam.ku...@uclmail.net
wrote:
I sure hope there are! Historians and classicists are increasingly
publishing to the web, and being unable to mark up years BCE in HTML 5
would
hinder this. That said, marking up a year, say 1992 AD, (as opposed to
Hey Jonas et al.:
Thanks for the reply, forgive my disbelief on Clarification 1. :) If
I'm completely with you, that is entirely unexpected on my part (and
I've read this part of the spec a few times). Is this to imply that,
no matter what the arguments to pushState(), if the path is
On Thu, Jul 30, 2009 at 8:43 AM, Elliotte Rusty
Haroldelh...@ibiblio.org wrote:
I note in http://www.whatwg.org/specs/web-apps/current-work/#valid-date-string
that Dates before the year zero can't be represented as a datetime in
this version of HTML. This seems a serious omission. Why can we
Jonas,
That is my interpretation too. But I think it's a little unclear whether
that means that the UA should update any Location fields in the UI. I
understand that this may be optional or outside the scope, but I think that
it should still be mentioned.
Now if the UA is suppose to update the
Gregg Tavares wrote:
If it's so clear, why do you think 2 of the 4 browsers that implemented
it apparently got it wrong?
Because the implementations preceded the current spec text; they were
just implementing something like Apple's Canvas without trying too
hard to be compatible in edge
Sorry, same domain policy is clearly defined. I just missed it.
Compare the resulting absolute URL to the document's address. If any part
of these two URLs differ other than the path, query, and fragment
components, then raise a SECURITY_ERR exception and abort the pushState()
steps.
On
Sebastian,
The same-origin is pretty clearly specified, I've included the excerpt
from the spec below. Your suggestion for clarity on updating Location
fields in the the UI would be a part of step five in the description
of pushState in section 6.10.2 is a good one. Ian, I feel like this
On Mon, Jul 27, 2009 at 3:29 AM, Jeremy Keithjer...@adactio.com wrote:
I concur. And I say that as someone who likes the XHTML-like syntax (always
closing tags, always quoting attributes, etc.). I don't think my personal
preference for writing markup should be enforced in the spec; it should
2009/7/30 Bruce Lawson bru...@opera.com
On Thu, 30 Jul 2009 15:05:10 +0100, Sam Kuper sam.ku...@uclmail.net
wrote:
I sure hope there are! Historians and classicists are increasingly
publishing to the web, and being unable to mark up years BCE in HTML 5
would
hinder this. That said,
On Thu, Jul 30, 2009 at 10:34 AM, Sam Kupersam.ku...@uclmail.net wrote:
2009/7/30 Bruce Lawson bru...@opera.com
On Thu, 30 Jul 2009 15:05:10 +0100, Sam Kuper sam.ku...@uclmail.net
wrote:
I sure hope there are! Historians and classicists are increasingly
publishing to the web, and being
On Thu, Jul 30, 2009 at 6:10 AM, Tab Atkins Jr.jackalm...@gmail.com wrote:
On Thu, Jul 30, 2009 at 12:54 AM, Garrett Smithdhtmlkitc...@gmail.com wrote:
HTML 5 defines input type=date as an input state. This is
implemented in at least one userAgent (Opera). Which other browsers
have implemented
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com
On Thu, Jul 30, 2009 at 10:34 AM, Sam Kupersam.ku...@uclmail.net wrote:
Not for BCE; I'm not working on that period at the moment, but excepting
that, here are a couple of good examples with ranges:
On Thu, Jul 30, 2009 at 11:12 AM, Sam Kupersam.ku...@uclmail.net wrote:
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com
On Thu, Jul 30, 2009 at 10:34 AM, Sam Kupersam.ku...@uclmail.net wrote:
Not for BCE; I'm not working on that period at the moment, but excepting
that, here are a couple of
At 17:12 +0100 30/07/09, Sam Kuper wrote:
2009/7/30 Tab Atkins Jr. mailto:jackalm...@gmail.comjackalm...@gmail.com
On Thu, Jul 30, 2009 at 10:34 AM, Sam
Kupermailto:sam.ku...@uclmail.netsam.ku...@uclmail.net wrote:
Not for BCE; I'm not working on that period at the moment, but excepting
At 11:16 -0500 30/07/09, Tab Atkins Jr. wrote:
1) Machine readability.
This begs the question.
raises the question. begging questions is assuming the answer in the
premise of the question.
Why do you need machine readability for the
dates in the Darwin journals? More specifically,
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com
On Thu, Jul 30, 2009 at 11:12 AM, Sam Kupersam.ku...@uclmail.net wrote:
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com
On Thu, Jul 30, 2009 at 10:34 AM, Sam Kupersam.ku...@uclmail.net wrote:
Not for BCE; I'm not working on that period at the
2009/7/30 David Singer sin...@apple.com:
Quite. We've had this debate before and Ian decided that it might be
confusing to apply a dating system to days when that dating system was not
in effect on those days, I think.
If by confusing you mean sufficiently confusing that it needs to be
On Thu, Jul 30, 2009 at 11:34 AM, David Singersin...@apple.com wrote:
At 11:16 -0500 30/07/09, Tab Atkins Jr. wrote:
1) Machine readability.
This begs the question.
raises the question. begging questions is assuming the answer in the
premise of the question.
I meant it in the sense
Can the historical-timeline community perhaps work with a microformat
for such things, so that we can standardize on the basis of experience
using the technology in the field, rather than on speculative uses?
Mike
On Thu, Jul 30, 2009 at 11:36 AM, Sam Kupersam.ku...@uclmail.net wrote:
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com
On Thu, Jul 30, 2009 at 11:12 AM, Sam Kupersam.ku...@uclmail.net wrote:
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com
On Thu, Jul 30, 2009 at 10:34 AM, Sam
On Thu, Jul 30, 2009 at 11:56 AM, Mike Shavermike.sha...@gmail.com wrote:
Can the historical-timeline community perhaps work with a microformat
for such things, so that we can standardize on the basis of experience
using the technology in the field, rather than on speculative uses?
I'd
2009/7/30 Tab Atkins Jr. jackalm...@gmail.com:
On Thu, Jul 30, 2009 at 11:56 AM, Mike Shavermike.sha...@gmail.com wrote:
Can the historical-timeline community perhaps work with a microformat
for such things, so that we can standardize on the basis of experience
using the technology in the
On Thu, 30 Jul 2009 19:01:33 +0200, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Jul 30, 2009 at 11:56 AM, Mike Shavermike.sha...@gmail.com
wrote:
Can the historical-timeline community perhaps work with a microformat
for such things, so that we can standardize on the basis of
On Tue, Jul 28, 2009 at 10:58 PM, Maciej Stachowiakm...@apple.com wrote:
Here's some security risks I've thought about, for persistent workers and
persistent background pages:
great list of risks
Thanks for the list, Maciej. However, Firefox extensions today have
all of the same problems. Do
On Wed, Jul 29, 2009 at 5:38 PM, Maciej Stachowiakm...@apple.com wrote:
* Notification Feeds *
Often, web applications would like to give users the option to subscribe to
notifications that occur at specific times or in response to server-side
events, and for the user to get these UI
On Thu, Jul 30, 2009 at 10:18 AM, Michael Davidson m...@google.com wrote:
On Tue, Jul 28, 2009 at 10:58 PM, Maciej Stachowiakm...@apple.com wrote:
Here's some security risks I've thought about, for persistent workers and
persistent background pages:
great list of risks
Thanks for the
On Thu, Jul 30, 2009 at 6:13 AM, Sebastian
Markbågesebast...@calyptus.eu wrote:
This suggestion seems similar to Digg's Stream project that uses multipart
documents: http://github.com/digg/stream
While it would be nice to have a way to parse and handle this in JavaScript,
it shouldn't be
It seems the biggest concern in this discussion is around BotNet
Construction Kit as Machej succulently called it, or an ability to run
full-powered platform API persistently in the background, w/o a visible
'page' in some window.
This concern is clear. But what could be a direction to the
Which browsers?
Thanks
-- dean
On Thu, Jul 30, 2009 at 2:04 AM, Ian Hicksoni...@hixie.ch wrote:
On Wed, 29 Jul 2009, Dean McNamee wrote:
For the curves, I don't really get the point of moveTo()ing to one of
the control points.
Me either, but at leave for quadratic and bezier curves, that
On Thu, Jul 30, 2009 at 3:51 PM, Dmitry Titov dim...@google.com wrote:
This concern is clear. But what could be a direction to the solution?
Assuming one of the goals for html5 is reducing a gap in capabilities
between web apps and native apps, how do we move forward with more powerful
APIs?
I think the error here is viewing this as a UX issue - if it were just a UX
issue, then the responses from people would be along the lines of Oh, this
sounds dangerous - make sure you wrap it with the same permissions UI that
we have for extensions, plugins, and binary downloads.
The realization I
On Thu, Jul 30, 2009 at 4:34 PM, Jim O'Donnellj...@eatyourgreens.org.uk wrote:
I think Google News Timeline is worth mentioning here as an application
which already does this
http://newstimeline.googlelabs.com/
It shows
events going back to the late Middle Ages. I'm not sure how they've
I think I almost get this distinction :-) you are saying that HTML+JS could
be made more powerful with new APIs, but only if it is done sufficiently far
from the 'regular web page browsing' experience (or model). Say, if it is a
browser extension or a prism-like app it's ok - only (or mostly)
On Thu, Jul 30, 2009 at 3:49 PM, Dmitry Titovdim...@google.com wrote:
I think I almost get this distinction :-) you are saying that HTML+JS could
be made more powerful with new APIs, but only if it is done sufficiently far
from the 'regular web page browsing' experience (or model). Say, if it
On Thu, Jul 30, 2009 at 3:45 PM, Aryeh Gregorsimetrical+...@gmail.com wrote:
On Thu, Jul 30, 2009 at 4:34 PM, Jim O'Donnellj...@eatyourgreens.org.uk
wrote:
I think Google News Timeline is worth mentioning here as an application
which already does this
http://newstimeline.googlelabs.com/
It
On Jul 30, 2009, at 10:18 AM, Michael Davidson wrote:
On Tue, Jul 28, 2009 at 10:58 PM, Maciej Stachowiakm...@apple.com
wrote:
Here's some security risks I've thought about, for persistent
workers and
persistent background pages:
great list of risks
Thanks for the list, Maciej.
2009/7/30 Aryeh Gregor simetrical+...@gmail.com
time certainly wouldn't help
here -- this application doesn't need a way to say this text string
denotes a particular time, but rather this event happened at this
particular time.
The latter presupposes the former. That's why being able to mark
Maciej Stachowiak wrote:
I'm not sure if I'd be totally comfortable with putting something as
streamlined as the Firefox extensions model. As presented on
http://addons.mozilla.org/, it seems fine - the extensions posted
there are centrally vetted and reviewed, the user has to take a clear
So use an out-of-band extension mechanism to establish trust and
permissioning for capabilities that fall out of bounds of the 'regular' web
model.
So lets put that to practice on this particular two-part proposal...
Our proposed solution has two parts.
This first part (below) falls within the
2009/7/29 Maciej Stachowiak m...@apple.com
On Jul 27, 2009, at 11:50 AM, Michael Davidson wrote:
Hello folks -
I'm an engineer on the Gmail team. We've been working on a prototype
with the Chrome team to make the Gmail experience better. We thought
we'd throw out our ideas to the list to
David Singer wrote:
Against that, one has to realize that the label of the day before X
is well-defined for the day before the introduction of the Gregorian
calendar, and iteratively going back to year 1, year 0, year -1, and
so on.
In neither the Gregorian nor the Julian calendars is there a
On Thu, 30 Jul 2009, Dean McNamee wrote:
Which browsers?
I was testing primarily Opera, Firefox, and Safari.
--
Ian Hickson U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,.
Things that are impossible just
On Sat, 18 Jul 2009, �istein E. Andersen wrote:
Non-semicolon-terminated entities that were conforming in HTML4, like
pi and mdash when they are not followed by a letter or digit (roughly
speaking), are currently expanded in Safari and Firefox, and requiring
this to change would be a
On Sat, 18 Jul 2009, Alex Bishop wrote:
There's a few parts of the specification of the StyleSheet object defined in
section 4.2.7 that are unclear to me.
The location (href DOM attribute)
For link elements, the location must be the result of resolving the
URL given by the element's
On Sat, 18 Jul 2009, Adam Barth wrote:
On Fri, Jul 17, 2009 at 4:10 PM, Ian Hicksoni...@hixie.ch wrote:
Suppose that there is a tool where someone can write some text, in which
case the text will be displayed when the page is loaded. Suppose that
whether the person has written this text is
On Sun, 19 Jul 2009, Eduard Pascual wrote:
On Sun, Jul 19, 2009 at 12:29 PM, Ian Hickson i...@hixie.ch wrote:
[...]
On Fri, 3 Jul 2009, Eduard Pascual wrote:
It's clear that, despite the spec would currently encourage this
example's markup, it is not a good choice. IMHO, either of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/30/09 7:26 PM, Michael Davidson wrote:
On Wed, Jul 29, 2009 at 5:38 PM, Maciej Stachowiakm...@apple.com wrote:
* Notification Feeds *
Often, web applications would like to give users the option to subscribe to
notifications that occur at
On Tue, 21 Jul 2009, Bil Corry wrote:
Ian Hickson wrote on 7/19/2009 5:39 AM:
On Wed, 15 Jul 2009, Bil Corry wrote:
I'm curious too, since the HTML5 draft itself says[1]:
-
This specification does not define how new values will get approved. It
is expected that the Wiki will
On Mon, 20 Jul 2009, David Wilson wrote:
2009/7/19 Ian Hickson i...@hixie.ch:
On Mon, 6 Jul 2009, Robert O'Callahan wrote:
When script creates an audio element using the new Audio constructor,
the 'autobuffer' attribute should be automatically set on that element.
Presumably scripts
On Mon, 20 Jul 2009, David Singer wrote:
At 10:45 + 19/07/09, Ian Hickson wrote:
On Fri, 3 Jul 2009, SJ Kissane wrote:
I am concerned by the wording of this section. There are different
systems of week number -- as far as I can work out, this is the same as
ISO 8601 week
On Mon, 20 Jul 2009 dar...@chaosreigns.com wrote:
Why is it okay for a document to not specify its HTML version?
That's the wrong question -- the more important question is why should we
specify the version of HTML that the author knew about when he started
writing the document?.
Do all
On Mon, 20 Jul 2009, Peter Kasting wrote:
Two unrelated comments.
First, it seems a bit odd to me that input type=email and input type=url
are validated (for typeMismatch problems) but input type=tel isn't. I
know it's prohibitively difficult to perfectly validate telephone number
formats
On Wed, Jul 29, 2009 at 6:49 PM, Kartikaya Gupta
lists.wha...@stakface.comwrote:
This behavior doesn't seem to be specced anywhere as far as I can tell.
Assuming the WEBADDRESSES spec referred to in HTML5 is the one at
http://www.w3.org/html/wg/href/draft.html that only says to trim
On Mon, 20 Jul 2009, Sylvain Pasche wrote:
1) What's the reason for preserving whitespace when a DOMTokenList
method is changing the attribute?
As a general rule, I try to make the APIs as minimally invasive as
possible. Whenever we have failed to do this, we end up confusing authors
--
On Mon, 20 Jul 2009, Jeff Walden wrote:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#concept-media-load-resource
When the user agent has completely fetched of the entire media resource
s/ of//
Fixed, thanks.
--
Ian Hickson U+1047E
On Tue, 21 Jul 2009, Remco wrote:
On Tue, Jul 21, 2009 at 6:27 AM, Jeff Waldenjwalden+wha...@mit.edu wrote:
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#concept-media-load-resource
When the user agent has completely fetched of the entire media resource
s/ of//
Am Freitag, den 31.07.2009, 00:26 + schrieb Ian Hickson:
On Mon, 20 Jul 2009, Nils Dagsson Moskopp wrote:
I second that motion, not only as owner of a smartphone, but also as
someone with webspace that has a volume cap. Automagic audio element
buffering could deter web authors from
Hi,
Several proposals have been made on this list in the past on how to
approach accessibility for the HTML5 video element.
I think the best way in which we can progress this is by doing an
implementation of a spec, discussing it, improving the spec, rinse and
repeat, which IIUC is the process
68 matches
Mail list logo
