John Fremlin wrote: > > "Leslie P. Polzer" <[email protected]> writes: >> On Aug 14, 11:20 am, John Fremlin <[email protected]> wrote: >> >>> One major issue is that if isearch box is marked dirty then when the >>> ajax call comes back, it will overwrite any further user input. This is >>> extremely annoying with slow AJAX. >>> >>> I would like to fix this before tidying up. Maybe the mixin approach is >>> wrong? >> >> I don't think the mixin approach is responsible for this. >> >> We rather seem to need a piece of custom Javascript to deal with this. >> Proposal after the AJAX request has completed: > > Am I correct in thinking that only dirty objects are updated by the AJAX > request?
That's right. Note that there's a basic dependency system for the dirty mechanism. > (If not that is a shame.) If so, then the trick is to make sure > that the filter input box is not marked dirty. My first idea, too. But I think the original isearch also gave feedback to the user, turning red when the search string couldn't be found. The only solution I see here is smart client-side code. >> 1. protect the text field against further modification > > That sounds rather irritating for the poor user. I don't think so. We're talking about a time span that will hardly be noticeable at all. > (2) On receipt of the AJAX answer, if the isearch contents have > changed, then do not apply but discard the AJAX answer (and potentially > make a new request). That would be another acceptable solution I guess. Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
