- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 May 2011 18:02:08 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12620 --- Comment #2 from Oscar Godson <oscargodson@gmail.com> 2011-05-06 18:02:07 UTC --- Just as an FYI, i posted this here because the form on the Web Storage spec doesnt work. It says I don't have JS enabled, which obviously, I do. It then sent me here... it was a feedback on the disk space section. I can post it elsewhere, I just figured this was the kind of feedback you were looking for...? If not, what kind of info are you looking for in those forms if its not about the spec? Not at all trying to be sarcastic or an ass, actually curious. Everyone says that it has to be synchronous but I honestly can't find that anywhere in the spec. It could be async easily and I actually don't understand why it couldnt? Also, yes, obviously allowing 1GB or unlimited data on all sites wouldn't work, but im just saying give the choice to the user. If, for example, photoshop.com needed 10GBs of data I would give it to them as I need it for the site and I know what its being used for. Now, if i go to some random site after googling something and it asks to store that much I would say no. I dont see what the issue is if its the user making the choice. Arent we making sites and browser for our end users? IndexedDB, again, is nice and powerful, but so, so, so much more complicated than localStorage. I'll learn it as it looks super cool, but for most stuff it seems like its a little heavy. Lastly, I know, I talked to the Chrome team awhile ago and, if you read my blog, they basically just called the entire idea of raising it even 5MBs stupid even tho all the other people aside from the Chrome team wanted it. They also said localStorage in general was just a stupid idea, so when I saw the suggestion box I thought it was the right place to do it. Sorry! -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 6 May 2011 18:02:09 UTC