[EMAIL PROTECTED]">*All* state is destroyed between profile changes. I believe issues here are covered in "kiosk" mode (not that we've entirely defined that yet). When I'm in a library, I certainly want scrollbar and form data to be preserved while I'm in my session.In article [EMAIL PROTECTED]"><[EMAIL PROTECTED]>, [EMAIL PROTECTED]
(Judson Valeski) wrote:I don't see why we'd want to special case scroll and form data entries
only (outside of maybe providing the ability to disable that kind of
history completely (note: I can't see any practical need for this right
now (unless of course saving those things is soooo expensive, *and* we
can't fix the size problem easily), everyone basically needs/wants that
kind of capability).
You'd want to turn this off for shared machines running in a public
place (e.g. a library).
[EMAIL PROTECTED]">No, but the way libraries currently work is, all bets are off unless you shut down the product. I don't see how you can isolate/determine/enforce certain caches (cookies, shist, ghist, password cache, single-sign on, wallet, etc) just *knowing* when to clear themselves (outside of a complete profile switch, which already clears out shist/ghist).Would you want someone to go back a few pages, and find your credit card number?
[EMAIL PROTECTED]">I think we're off in the weeds. What was wrong w/ the ghistory LRU algo used in 4.x (hang onto entries for X days)?Clearing history, from a users perspective, is
always _time_ based, not "have I filled out a form" based."Time" in "I did that more than 30 mins ago, I expect my machine
to forget it"? Or some other measure of time? I think a 'number
of URLs ago' is a better condition. If you're interrupted in the
middle of placing an Amazon order, and come back 2 hours later,
then find you want to back up and fix a typo on the past page,
you don't want wallclock-time based history clearing.
What kind of notification mechanism are you proposing for shist cleanup (beyond memory pressure observation)? Perhaps if you go into more detail I'll get the perspective I need here.
Jud
[EMAIL PROTECTED]">
