Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: garlic.js - don't let your users lose their form data

guillaumepotier.github.com

Post reply on HN
Print view View original

61–70 of 109 posts

Re: Show HN: garlic.js - don't let your users lose their form data

#61

Post by recuter »

fruchtose wrote: post #5

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…

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.

Re: Show HN: garlic.js - don't let your users lose their form data

#62

Post by wildgift »

salman89 wrote: post #45

Should add an option for users to disable this (like remember me on login forms)... not good for public computers if you don't know the form you just filled in but didn't submit will retain the data. Other than that, cool!

Persisting localStorage seems to be controlled by the setting to delete cookies after exiting the browser. If i have it set to delete cookies, it deletes localStorage. if i allow it to keep cookies after quitting the browser, then it persists localStorage.

(Noticed this because the demo failed for me the first time.)

Re: Show HN: garlic.js - don't let your users lose their form data

#64

Post by wildgift »

ceejayoz wrote: post #42
csmatt wrote: post #23

I was thinking about this the other day and I thought "How is this not standard!?" Good job!

It's not standard because people frequently do things like type a credit card number into a form on a public computer. Lots of potential for privacy breaches.

Even on a private computer, having it stored in a file can be bad, because if another process gets on there and reads the storage, it'll get the data.

Re: Show HN: garlic.js - don't let your users lose their form data

#65

Post by jarin »

StavrosK wrote: post #59
vidarh wrote: post #37

Earlier quoted context omitted.

> It seems that everything requires jQuery these days And there's your answer: The "cost" of depending on jQuery is small since so many things depend on it that most potential users probably already pull it in.

That's true, I guess. I just don't think you should include large dependencies if you can easily avoid them.

It really doesn't matter, if you use a version of jQuery that is likely to already be cached (like the ones hosted at Google Code).

Re: Show HN: garlic.js - don't let your users lose their form data

#66

Post by jarin »

StavrosK wrote: post #60
seabee wrote: post #39

Earlier quoted context omitted.

Ideally this would be solved in a similar way as when you statically link to libraries in C - the parts of your dependency are pulled in and users don't have to worry about it. (There are other issues with this of course, but they are well understood by now that someone could develop a system to mitigate that by now)

The problem is more about the download size than the actual deployment (unless you mean using only the parts of jQuery you need, in which case I guess it would be hard to share between apps).

You're better off using the full jQuery hosted at a common CDN, since it is likely to already be cached on the user's computer.

Re: Show HN: garlic.js - don't let your users lose their form data

#67

Post by SquareWheel »

anothermachine wrote: post #47
LearnYouALisp wrote: post #9

> don't let your users lose their form data This is a huge problem, and is the reason I've had Lazarus installed for a few years now. https://addons.mozilla.org/en-us/firefox/addon/lazarus-form-... Apparently it exists for Chrome now, too.

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.

Re: Show HN: garlic.js - don't let your users lose their form data

#68

Post by jarin »

recuter wrote: post #61
fruchtose wrote: post #5

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…

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.

Re: Show HN: garlic.js - don't let your users lose their form data

#69

Post by zapt02 »

paulirish wrote: post #15
fruchtose wrote: post #5

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…

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...

say that to some my sites that still see >50% IE6/7 share. It all depends on your demographic.

Re: Show HN: garlic.js - don't let your users lose their form data

#70

Post by ErrantX »

fruchtose wrote: post #5

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…

This library solves a problem and solves it well. The local storage issue should be left up to other libraries who are designed to solve that gripe. :-)
Post reply on HN