On Tue, 7 Dec 2010, Boris Zbarsky wrote:
On 12/7/10 5:10 PM, Ian Hickson wrote:
Per spec, currently document.open() replaces the current page rather
than allow navigation.
I believe there are cases where that would cause us to break compat.
Note that neither IE nor Gecko does a replace
On Tue, 24 Aug 2010, Boris Zbarsky wrote:
On 8/24/10 6:13 PM, Ian Hickson wrote:
So basically, translating this to specese:
Document objects on which you call open() have an override reload
flag set and an initially empty source cache added.
When you call
On 12/7/10 5:10 PM, Ian Hickson wrote:
Per spec, currently document.open() replaces the current page rather than
allow navigation.
I believe there are cases where that would cause us to break compat.
Note that neither IE nor Gecko does a replace load there, last I checked.
I'm not sure how
On Tue, 27 Jul 2010, Boris Zbarsky wrote:
On 7/27/10 3:00 PM, Ian Hickson wrote:
On each document.write() on a document.open()ed document, Gecko
appends the written string to a cache entry (at the method call
time--not at the tokenization time--which makes a difference of the
On 8/24/10 6:13 PM, Ian Hickson wrote:
So basically, translating this to specese:
Document objects on which you call open() have an override reload
flag set and an initially empty source cache added.
When you call document.write() on a document with the override reload
flag
On Tue, 30 Mar 2010, Henri Sivonen wrote:
The spec says about location.reload():
Navigate the browsing context to the document's current address with
replacement enabled. The source browsing context must be the browsing
context being navigated.
It appears that this is what WebKit and
On 7/27/10 3:00 PM, Ian Hickson wrote:
On each document.write() on a document.open()ed document, Gecko appends
the written string to a cache entry (at the method call time--not at the
tokenization time--which makes a difference of the document loads
external scripts that also call
On 7/27/10 4:10 PM, Boris Zbarsky wrote:
Does document.open() clear the cache entry?
It creates a new one and unpins the old one.
Note: the unpinning may or may not happen her depending on what session
history does; I haven't double-checked this part.
-Boris
On Mar 30, 2010, at 7:38 AM, Henri Sivonen wrote:
The spec says about location.reload():
Navigate the browsing context to the document's current address
with replacement enabled. The source browsing context must be the
browsing context being navigated.
It appears that this is what WebKit
On 3/30/10 10:38 AM, Henri Sivonen wrote:
This makes me wonder: If the two engines with the largest market
share both take steps to enable document.open()ed docs to be
reloaded, is the behavior needed for optimal Web compatibility?
At one point, yes. I don't recall many bug reports about this
10 matches
Mail list logo
