On Sat, Nov 14, 2009 at 5:23 PM, timeless wrote:
> what if pushState returned a value which could be passed to clearState?
On Sun, Nov 15, 2009 at 3:44 AM, Justin Lebar wrote:
> I'm not sure how this would work. What would clearState do with that value?
roughly:
user visits http://app.example
On Sat, Nov 14, 2009 at 5:23 PM, timeless wrote:
> what if pushState returned a value which could be passed to clearState?
I'm not sure how this would work. What would clearState do with that value?
> (i can't find clearState in
> http://www.whatwg.org/specs/web-apps/current-work/#dom-history-p
what if pushState returned a value which could be passed to clearState?
https://wiki.mozilla.org/Firefox_3.6/PushState_Security_Review was
interesting (i can't find clearState in
http://www.whatwg.org/specs/web-apps/current-work/#dom-history-pushstate
-- maybe i'm looking in the wrong place?)
On Thu, Nov 12, 2009 at 4:54 PM, Brady Eidson wrote:
>
> On Nov 12, 2009, at 4:39 PM, Jonas Sicking wrote:
>
>> On Thu, Nov 12, 2009 at 1:08 PM, Brady Eidson wrote:
>>> I think clearState() is a good idea but is just spec'ed poorly.
>>>
>>> Imagine the use case of the checkout procedure at an onl
Sorry to self-reply. I just want to make four targetted points:
-As is, the language specifying clearState() has gapping holes that prevent us
from agreeing on what it is we're implementing.
-I personally think the intention of clearState() is useful and not a bad idea,
and that a more fine gr
On Nov 12, 2009, at 4:39 PM, Jonas Sicking wrote:
> On Thu, Nov 12, 2009 at 1:08 PM, Brady Eidson wrote:
>> I think clearState() is a good idea but is just spec'ed poorly.
>>
>> Imagine the use case of the checkout procedure at an online merchant.
>>
>> There's normally steps like "enter your
On Thu, Nov 12, 2009 at 1:08 PM, Brady Eidson wrote:
> I think clearState() is a good idea but is just spec'ed poorly.
>
> Imagine the use case of the checkout procedure at an online merchant.
>
> There's normally steps like "enter your address," "choose your shipping
> method," "enter your CC in
On Nov 12, 2009, at 3:37 PM, Marius Gundersen wrote:
>
>
> On Fri, Nov 13, 2009 at 8:16 AM, Brady Eidson wrote:
> I should've responded to this more directly:
>
> On Nov 12, 2009, at 12:00 PM, Justin Lebar wrote:
>
> > I think the use case I proposed is much better served by something
> > li
On Fri, Nov 13, 2009 at 8:16 AM, Brady Eidson wrote:
> I should've responded to this more directly:
>
> On Nov 12, 2009, at 12:00 PM, Justin Lebar wrote:
>
> > I think the use case I proposed is much better served by something
> > like history.truncate(numBefore, numAfter), which would remove all
On Thu, Nov 12, 2009 at 1:08 PM, Olli Pettay wrote:
> On 11/12/09 10:00 PM, Justin Lebar wrote:
>>
>> Perhaps a better idea is leaving this whole issue to the UA, which
>> could collapse all the entries from a single origin in the UI. Then
>> we wouldn't need either function.
>
> How would UA col
I should've responded to this more directly:
On Nov 12, 2009, at 12:00 PM, Justin Lebar wrote:
> I think the use case I proposed is much better served by something
> like history.truncate(numBefore, numAfter), which would remove all but
> the numBefore entries before the current entry and the num
On 11/12/09 10:00 PM, Justin Lebar wrote:
Perhaps a better idea is leaving this whole issue to the UA, which
could collapse all the entries from a single origin in the UI. Then
we wouldn't need either function.
How would UA collapse entries from a single origin?
I agree clearState is a bit
I think clearState() is a good idea but is just spec'ed poorly.
Imagine the use case of the checkout procedure at an online merchant.
There's normally steps like "enter your address," "choose your shipping
method," "enter your CC info," and finally "place your order." It'd be pretty
neat if th
As I alluded to in the thread "AJAX History Concerns," I'm not
convinced that we need the history.clearState() function.
I haven't been able to come up with a compelling case where a page
would use this. I guess the idea is that I'm on Google Maps, which is
using pushState to make a history entry
14 matches
Mail list logo
