Live data from Hacker News

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

guillaumepotier.github.com

21–30 of 109 posts

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

#21

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

That depends on your user base. If it's just the wider internet that's accurate, but if you're aiming at government or big corporate clients, you'd better check your analytics first.

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

#22

Is there a way to differentiate between data that's only saved using Garlic (local) vs data that's also been saved to the server? This could be a huge confusion for users if there isn't.

Yes, I'll need to work on that, if there is already server data. Maybe in a tooltip like, let the user choose which version he should use

Could you add a version number to your script for this reason? It'll also make diff'ing much easier.

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

#24

Is there a way to differentiate between data that's only saved using Garlic (local) vs data that's also been saved to the server? This could be a huge confusion for users if there isn't.

Yes, I'll need to work on that, if there is already server data. Maybe in a tooltip like, let the user choose which version he should use

I wonder if you should have some sort of icon or text indicator (per field) that shows there is saved form data available, but don't populate until the user triggers it, or an option to restore all available form data in one click? There are situations where I want to clear a form so I'll refresh the page if a clear option isn't available. I guess the solution would be for everyone that uses garlic.js to make sure they have a clear option.

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

#25

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

One of the sites I built recently has a ton of backbone.js dynamic loading. I tried to test it in IE 6, and the browser just immediately crashes. Not like an alert box, just an instant shut down! In the past I would have started the unpleasant task of figuring that out and fixing it up, or perhaps detecting and redirecting to a more lightweight page. This time I said screw it - I'm done with IE 6! Call me irresponsib…

I think you're within your right to ditch IE6. I don't even support IE7, users just get a chromeframe prompt.

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

#26

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

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

#28

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 figure those folks using IE 6 or 7 are used to a lackluster internet experience. Little perks like this are not critical features and can be foregone for this small userbase.

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

#29

Is there a way to differentiate between data that's only saved using Garlic (local) vs data that's also been saved to the server? This could be a huge confusion for users if there isn't.

Yes, I'll need to work on that, if there is already server data. Maybe in a tooltip like, let the user choose which version he should use

There are all sorts of use cases that might want one thing over the next (display server data vs local data for example).

Keep you API open and flexible for the UX designer to choose what's best when. Also, if it's showing local data do something simple, like give the field a class of "garlic-data". That way the UX designer can choose the best way to differentiate it for their use case.

Post reply on HN