On Tue, Jul 19, 2011 at 2:08 PM, Robby Findler <[email protected]>wrote:
> On Tue, Jul 19, 2011 at 1:06 PM, Eli Barzilay <[email protected]> wrote: > > Yesterday, Robby Findler wrote: > >> Also, when I disable cookies, I see that the context sensitive > >> search just silently doesn't work. > >> > >> Would it be possible to always have the search set a (separate) > >> cookie and give a warning if it doesn't find the (constant) cookie? > > > > I think that it's far more likely that JS fails, so you won't see any > > warning anyway. > > JS could also hide a warning that JS wasn't available, right? > > > As for a warning when chrome prevents storing a cookie, I remember > > trying that and IIRC it can't even tell when you're not allowed to > > store a cookie. > > Yeah, I can see how they'd set things up like that. I have JS and Cookies enabled on both browsers, so that's not the problem. >> I don't understand the last bit about refreshing and reseting the >> cookie. What problem is this second trampoline trying to fix? > >page it will re-set the cookie. The trampoline page is therefore >If you keep the "hq=blah" in the URL, then whenever you visit that >setting the cookie and then takes you further to the usual search page >without the parameter being part of the URL. and why are we using cookies?
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
