81–90 of 109 posts
Earlier quoted context omitted.
I get the sentiment here but considering this is an enhancement to the user experience that IE6/7 users will never know they missed out on either way... You don't need to backport everything, only the critical stuff.
It also probably wouldn't be super crazy difficult to use a Flash local storage fallback for them.
Earlier quoted context omitted.
Thinking about it, I'm mildly amazed that the browsers themselves didn't solve this problem back in 1996 or so.
Opera saves forms when possible. It also has instant backward navigation from cache. I guess it saves forms on cached pages.
I think the desire for this kind of project is very reasonably based, and it looks like you have done great work on most of the implementation. I have one gripe with it, though. It would be nice if the documentation mentioned that garlic.js requires an HTML5 browser with localStorage implemented. Remember, there are people who are still using Internet Explorer 6 and 7, and these browsers are incompatible [1]. This is…
Yes, I'll definitely re-work on both the code and the doc. I've read that there is a kind of localStorage portage for IE8- that I'll look into. Currently, if the browser does not support localStorage, the plugin auto-disable. Best
Which leads me to an aside — Why did you choose localStorage over sessionStorage?
For those who don't know — local/session are the same, only session will be cleared when the browser is closed.
My browser already auto completes form data… so I'm not sure I'd need it between sessions.
Earlier quoted context omitted.
Yes, I'll definitely re-work on both the code and the doc. I've read that there is a kind of localStorage portage for IE8- that I'll look into. Currently, if the browser does not support localStorage, the plugin auto-disable. Best
IE8 supports both local and sessionStorage. Which leads me to an aside — Why did you choose localStorage over sessionStorage? For those who don't know — local/session are the same, only session will be cleared when the browser is closed. My browser already auto completes form data… so I'm not sure I'd need it between sessions.
Earlier quoted context omitted.
IE8 supports both local and sessionStorage. Which leads me to an aside — Why did you choose localStorage over sessionStorage? For those who don't know — local/session are the same, only session will be cleared when the browser is closed. My browser already auto completes form data… so I'm not sure I'd need it between sessions.
what about when the browser crashes?
While convenient and technically fine, this can get creepy for users. “Wait, I didn't submit the form on purpose but the data has been saved?”
Like many UX features similar to this, I would say it mainly comes down to who your audience is, and where it's being used on how "weirded out" users would feel by this feature.
Earlier quoted context omitted.
For all intents and purposes, IE6 and IE7 are dead. They account for less than 1.5% of worldwide browsers [1]. At this point, seems okay to leave out. [1] http://gs.statcounter.com/#browser_version_partially_combine...
Sure you can quote stats all day, but it depends on your target audience. If you are running a tech website (such as HN/TC/Reddit/etc) you will see a HUGE portion of visitors using browsers like Chrome/Firefox and hardly any IE. However if you are building websites that regular people use they still use XP and IE7... so much so that it can account for 10-30% of your website traffic.. It really pains me when HTML fram…
Earlier quoted context omitted.
Form content recall is a native Chrome feature now.
Do you have a link? I've followed Chrome development pretty closely and have never seen that. I too use Lazarus.