On Fri, 3 Apr 2009, Julian Reschke wrote:
But maybe it is. Checking references earlier catches problems earlier.
It's WHATWG policy to not fill in the references section until a spec is
basically complete. For HTML5 this is scheduled for August.
--
Ian Hickson U+1047E
Hi
Havent read it all yet, but I did a search, and found nothing about
the keygen element.
Isnt that suposed to be in there, or do you miss documentation on it?
If you are missing documentation, I will be happy to try to write
something in the same format as the other tags..
Thanks
Regards
On Fri, 03 Apr 2009 06:26:43 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
Mozilla could probably get behind that, but I don't know who else is
willing to bite the bullet.
The problem already exists for document.cookie, no? And the current API is
by far the most convenient the use.
The word string is misspelled as stirng here:
http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-meta-http-equiv-refresh
It's the last word at point #18.
Woohoo, I'm gonna be famous! I'll try to do more at a time from now
on, just wanted to secure my place in history.
On Fri, Apr 3, 2009 at 2:18 AM, Anne van Kesteren ann...@opera.com wrote:
On Fri, 03 Apr 2009 06:26:43 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
Mozilla could probably get behind that, but I don't know who else is
willing to bite the bullet.
The problem already exists for
On Thu, Apr 2, 2009 at 8:37 PM, Robert O'Callahan rob...@ocallahan.org wrote:
I agree it would make sense for new APIs to impose much greater constraints
on consumers, such as requiring them to factor code into transactions,
declare up-front the entire scope of resources that will be accessed,
I'm suggesting an addition to cross-domain (i)frames that allows scrolling
specific content into view. The use case is sites that aggregate data from
many sites (e.g. search engines) and want to display that data in an iframe.
They can load the page in an iframe, but they have no way to make the
I know I said I would stay out of this conversation, but I feel obliged to
share a data point that's pertinent to our API design.
The structured storage spec has an asynchronous API currently. There are no
shortage of experienced javascript programmers at Google, and yet the single
biggest piece
On Fri, Apr 3, 2009 at 2:25 PM, Drew Wilson atwil...@google.com wrote:
If we can capture the correct behavior using synchronous APIs, we should.
I think we already have a good, correct, synchronous API. My concern is the
implications to the internals of the implemenation.
Anyway, given that
On Sat, Apr 4, 2009 at 6:35 AM, Jeremy Orlow jor...@google.com wrote:
If I understood the discussion correctly, the spec for document.cookie
never stated anything about it being immutable while a script is running.
Well, there never was a decent spec for document.cookie for most of its
life,
I created a page that sets a variable in sessionStorage, then I navigated to
a different domain, then I went back to the page and checked if the variable
was still set. In Safari 4 (beta) it is. In IE8 it isn't.
The spec is not terribly clear: When a top-level browsing context is
destroyed (and
On Fri, 3 Apr 2009, Jeremy Orlow wrote:
I created a page that sets a variable in sessionStorage, then I
navigated to a different domain, then I went back to the page and
checked if the variable was still set. In Safari 4 (beta) it is. In
IE8 it isn't. The spec is not terribly clear: When
On Fri, Apr 3, 2009 at 2:49 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
On Sat, Apr 4, 2009 at 6:35 AM, Jeremy Orlow jor...@google.com wrote:
People are now talking about specifying this, but there's been push back.
Also, there's no way to guarantee serializability for the network
On Fri, Apr 3, 2009 at 3:16 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 3 Apr 2009, Jeremy Orlow wrote:
I created a page that sets a variable in sessionStorage, then I
navigated to a different domain, then I went back to the page and
checked if the variable was still set. In Safari 4
On Fri, Apr 3, 2009 at 3:16 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 3 Apr 2009, Jeremy Orlow wrote:
I created a page that sets a variable in sessionStorage, then I
navigated to a different domain, then I went back to the page and
checked if the variable was still set. In Safari 4
On Fri, Apr 3, 2009 at 5:03 PM, Darin Fisher da...@chromium.org wrote:
Hmm...
In Chrome we also create a new browsing context when the user types a new
URL into the location bar of an existing tab. This can be thought of as a
shortcut for create a new tab with the given URL and close the old
On Fri, 3 Apr 2009, Darin Fisher wrote:
In Chrome we also create a new browsing context when the user types a new
URL into the location bar of an existing tab.
So a user can't hit the back button after typing in a URL?
The term browsing context in the spec basically corresponds to the
Ian Hickson wrote:
The term browsing context in the spec basically corresponds to the
session history exposed by window.history, and the outer Window object
that the history is on.
How should this behave in a situation like Firefox's undo close tab,
where the resulting tab has a brand-new
On Fri, 3 Apr 2009, Boris Zbarsky wrote:
Ian Hickson wrote:
The term browsing context in the spec basically corresponds to the
session history exposed by window.history, and the outer Window
object that the history is on.
How should this behave in a situation like Firefox's undo close
I think this also applies: NOTE: The lifetime of a browsing context can be
unrelated to the lifetime of the actual user agent process itself, as the
user agent may support resuming sessions after a restart.
On Fri, Apr 3, 2009 at 6:46 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 3 Apr 2009,
Ian Hickson wrote:
However, the Web Storage spec allows for this case:
| When a new top-level browsing context is created by cloning an existing
| browsing context, the new browsing context must start with the same
| session storage areas as the original, but the two sets must from that
|
Ojan Vafai:
2) Add a css or xpath expression to fragment identifiers. Tthe iframe
src can be set to http://foo.com#css(.foo #bar). Same as above
applies. If there's no match, it's a noop. If there is a match, it
scrolls the first one into view.
Sounds like XPointer:
22 matches
Mail list logo
