On Thu, 16 Feb 2012, Justin Lebar wrote:
On Wed, Feb 15, 2012 at 5:31 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 15 Feb 2012, Justin Lebar wrote:
- It sets the document's current address to .../page.html#foo.
Well, this is pretty bad. document.location is the document's current
From an author's point of view, there's no such thing as the
document's original URI and, unless you're a nerd, you've never heard
of the base URI. There's just the document's URI, modified by
pushState.
From this point of view, I'd say it's less surprising that relative
URIs would break
On 20/02/12 2:35 PM, Sean Hogan wrote:
On 16/02/12 5:03 PM, Justin Lebar wrote:
On Wed, Feb 15, 2012 at 5:31 PM, Ian Hicksoni...@hixie.ch wrote:
On Wed, 15 Feb 2012, Justin Lebar wrote:
- It sets the document's current address to .../page.html#foo.
Well, this is pretty bad.
On 16/02/12 5:03 PM, Justin Lebar wrote:
On Wed, Feb 15, 2012 at 5:31 PM, Ian Hicksoni...@hixie.ch wrote:
On Wed, 15 Feb 2012, Justin Lebar wrote:
- It sets the document's current address to .../page.html#foo.
Well, this is pretty bad. document.location is the document's current
address
On Wed, 20 Jul 2011, Justin Lebar wrote:
The spec as written decides whether a link is a same-resource
reference or not based on comparing the URLs to what you're calling
the original address, not comparing it to the current address. See the
navigation algorithm, step 7 /Fragment
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1342
It doesn't make sense that the second image is broken.
(For some reason in Firefox I get an exception. Not sure if I'm misusing
the API or if it's a bug in Firefox.)
Not sure what's going on with that Firefox exception. But
On Wed, 15 Feb 2012, Justin Lebar wrote:
Hm...maybe you're right. But then, how do we jive this with #foo and
?foo links, both of which resolve relative to the current URI in both
Firefox and WebKit?
We fix the implementations to match the spec. :-)
- It sets the document's current
On Wed, Feb 15, 2012 at 5:31 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 15 Feb 2012, Justin Lebar wrote:
- It sets the document's current address to .../page.html#foo.
Well, this is pretty bad. document.location is the document's current
address [1]. So clicking #foo changed
The spec as written decides whether a link is a same-resource reference or
not based on comparing the URLs to what you're calling the original
address, not comparing it to the current address. See the navigation
algorithm, step 7 /Fragment identifiers/.
Maybe I'm misunderstanding, but this
On Wed, 27 Apr 2011, Justin Lebar wrote:
The document base URL is used when fetching resources.
Right now, if a page doesn't have a base element, the document base
URL is set to the document's address. (I'm going to call this the
document's original address.) The document's original
The document base URL [1] is used when fetching resources.
Right now, if a page doesn't have a base element, the document base
URL is set to the document's address. (I'm going to call this the
document's original address.) The document's original address does
not change when you call pushState;
11 matches
Mail list logo