There&#39;s no difference in Chrome, but i recommend using localStorage.removeItem(key) so that you get in the habit of doing so.  That way, when you go to use localStorage in a website, you are already using the method that is most likely to work with shims and polyfills for outdated browsers.

I&#39;m trying to use the simplest possible scenario using a date picker in different browsers. I suspect I&#39;m doing something very simple the wrong way but after lots of searching around I still haven&#39;t found a solution. Below is some sample code that represents what I&#39;m attempting.

If I use Chrome (v12.0.742.122) and pick a date from the picker like 13/08/2011 the jQuery validation logic will not allow the page to submit even though I&#39;ve explicitly specified the format as &#39;dd/mm/yy&#39;. 

If I change the format to &#39;dd/M/yy&#39; and choose a date like 13/Aug/2011 it works in Chrome but then won&#39;t submit for me in IE (v8.0.7600.16385). In FireFox (v3.6.18) both formats work.

What validation script do I need to be able to support date formats of &#39;dd/mm/yy&#39; in Chrome?

	&lt;html&gt;
	 &lt;head&gt;
	  &lt;link rel=&quot;stylesheet&quot; type=&quot;text/css&quot; href=&quot;jquery-ui.css&quot; /&gt;
	  &lt;script type=&quot;text/javascript&quot; src=&quot;jquery-1.4.4.js&quot;&gt;&lt;/script&gt;
	  &lt;script type=&quot;text/javascript&quot; src=&quot;jquery.validate.js&quot;&gt;&lt;/script&gt;
	  &lt;script type=&quot;text/javascript&quot; src=&quot;jquery.validate.unobtrusive.js&quot;&gt;&lt;/script&gt;
	  &lt;script type=&quot;text/javascript&quot; src=&quot;jquery-ui.js&quot;&gt;&lt;/script&gt;
	  &lt;script type=&quot;text/javascript&quot;&gt;
	      $(document).ready(function () {
		$(&#39;.date&#39;).datepicker({ dateFormat: &#39;dd/mm/yy&#39; });
                $.validator.addMethod(&quot;dateRule&quot;, function(value, element) {
		  return true;
		},
		&quot;Error message&quot;);
	      });
	  &lt;/script&gt;
	 &lt;/head&gt;
	 &lt;body&gt;
		&lt;form&gt;
			Date: &lt;input type=&quot;text&quot; name=&quot;myDate&quot; class=&quot;date dateRule&quot; /&gt;
			&lt;input type=&quot;submit&quot; /&gt;
		&lt;/form&gt;
	 &lt;/body&gt;
	&lt;/html&gt;

Unobtrusive validation in Chrome won&#39;t validate with dd/mm/yyyy

I have seen variables like _ image and was wondering what _ meant?

Why do we use _ in variable names?

I&#39;m using `localStorage` in a Chrome extension.

Is there any difference between `delete localStorage[key]` and `window.localStorage.removeItem(key)` or do they behave identically?

Note that I choose `window.localStorage.removeItem(key)` to correspond exactly to the [spec][1], but `localStorage.removeItem(key)` is how it would probably look in the wild.


  [1]: http://dev.w3.org/html5/webstorage/#the-localstorage-attribute

Deleting from localStorage: should I use delete or .removeItem?

I'm using <code>localStorage</code> in a Chrome extension.
Is there any difference between <code>delete localStorage[key]</code> and <code>window.localStorage.removeItem(key)</code> or do they behave identically?
Note that I choose <code>window.localStorage.removeItem(key)</code> to correspond exactly to the <a href="http://dev.w3.org/html5/webstorage/#the-localstorage-attribute" target="_blank" rel="noopener noreferrer">spec</a>, but <code>localStorage.removeItem(key)</code> is how it would probably look in the wild.

I am developing a front end of a web app using NetBeans IDE 7.0.1. Recently I had a very nasty bug, which I finally fixed.

Say I have code

    var element = &#39;&lt;input size=&quot;3&quot; id=&quot;foo&quot; name=&quot;elements[foo][0]&quot; /&gt;&#39;;
    $(&#39;#bar&#39;).append(element);

I noticed that something gone wrong when I saw that `size` attribute doesn&#39;t work in Chrome (didn&#39;t checked in other browsers). When I opened that element in Inspector, it was interpreted as something like

    &lt;input id=&quot;&amp;quot;3&amp;quot;&quot; name=&quot;&amp;quot;elements[foo][0]&amp;quot;&quot; 
        size=&quot;&amp;quot;foo&amp;quot;&quot; /&gt;

Which was rather strange. After manually retyping the `element` string character-in-character, the bug was gone. When I undo&#39;ed that change I noticed that Netbeans alerted me about some Unicode characters in my old code. It was `\u200b` - a zero width spaces after each &#39;=&#39;, between &#39;][&#39; and in the end of the string. So the string appeared normal because zero width spaces wasn&#39;t displayed, but after escaping them my string was

    &#39;&lt;input size=\u200b&quot;3&quot; id=\u200b&quot;foo&quot; name=\u200b&quot;elements[foo]\u200b[0]&quot; /&gt;\u200b&#39;

Now where the hell did I get them?

I&#39;m not sure where did I copied the code of `element` from, but it&#39;s definitely one of the following:

 - Other pane of Netbeans Editor with HTML template file;
 - Google Chrome Inspector, &#39;Copy as HTML&#39; action;
 - Google Chrome source view page (very doubtfully).

But I can&#39;t reproduce the bug with neither of that.

I use Netbeans 7.0.1 and Google Chrome 13.0 under Windows 7. No keyboard switchers or anything like it is running. Also I&#39;m using Git for version control, but I didn&#39;t pulled that code, so it is very unlikely that Git is to blame. It can&#39;t be a stupid joke of my colleagues, because they are quite well-mannered.

Any suggestions who messed up my code?

\u200b (Zero width space) characters in my JS code. Where did they come from?

I really like the ability to edit javascript in the chrome debugger however, I find that it can be really problematic getting the debugger to re-fetch the JavaScript from the server.

Sometimes I have to go as far just closing the debugger and reloading the frame works OK - but other times (an dI cannot pin down under what conditions this occurs) I have to clear my temporary internet cache.  Sometimes I swear I have to close chrome completely, then clear the cache and then load the page before the debugger finally shows me the most up-to-date script.

(NB.  There is no caching of the script by the web server)

I was wondering if anyone knew of a quick and easy way to tell the debugger to invalidate all its javascript and fetch it all anew on page reload?

How to force Chrome&#39;s script debugger to reload javascript?

For some reason, the prototype framework (or another JavaScript code) that is shipped with [Magento][1] is replacing standard console functions, so I can&#39;t debug anything. Writing down in JavaScript console `console` I get the following output:

    &gt; console
    Object
    assert: function () {}
    count: function () {}
    debug: function () {}
    dir: function () {}
    dirxml: function () {}
    error: function () {}
    group: function () {}
    groupEnd: function () {}
    info: function () {}
    log: function () {}
    profile: function () {}
    profileEnd: function () {}
    time: function () {}
    timeEnd: function () {}
    trace: function () {}
    warn: function () {}

I&#39;m using `Google Chrome version 13.0.782.112` on Linux.

`Prototype JavaScript framework, version 1.6.0.3`

Is there a quick way to solve this?

  [1]: http://en.wikipedia.org/wiki/Magento


Restoring console.log()

Referred to as the &quot;JavaScript console&quot;, when you click on a link, the log is cleared.

Is there a way to stop this log from being cleared when you click on a link?

The problem is that an event triggered onClick is returning an error which makes it harder to diagnose because the error is only displayed for a short time before being cleared.

Thanks.

Stop the console log clearing when you click a link in Google Chrome

What is the difference between the &#39;self&#39; and &#39;total&#39; columns in the Chrome CPU profiling of JS code?

![enter image description here][1]


  [1]: http://i.stack.imgur.com/JRFqN.png

Difference between &#39;self&#39; and &#39;total&#39; in Chrome CPU Profile of JS

Is there any way to reset/clear browser&#39;s localStorage in javascript?

Clearing localStorage in javascript?

When my app stores data locally on a phone, how permanent is that storage? I&#39;ll elaborate the exact situation:

I&#39;m building an app with jQueryMobile and Phonegap. It&#39;s essentially a browser app, but using Phonegap lets me package it and sell it in the app stores, among other advantages.

Phonegap offers two ways of storage, both of which functions harmonize native functions of iOs, Android, Blackberry and some other OSs: localStorage (which is primitive key-value pairs), and a Web SQL database. 
Both localStorage and web SQL are forms of storage that belong to the browser. Having said that, I can&#39;t find out how long the data will stay stored, under what circumstances it will be deleted, under what circumstances it may not be available, etc.

For example, if the app stores data with localStorage or web SQL, and the user switches to a different standard browser on their Android, will the app be opened with the new browser and does that mean that the stored data is unavailable?

If the user doesn&#39;t use the app for a year (which in my case is a realistic and not necessarily a bad scenario), will the data have expired like a cookie, or maybe been pushed out of the browser&#39;s storage by a deluge of data from other apps?

Or will the data be destroyed even earlier, such as when:
- user visits another site in the browser
- browser is manually closed
- browser process is killed or dies
- etc

Or are localStorage and web SQL the kind of storage that you only delete when (in Android) you go to Settings &gt; Apps and actively remove the user data associated with the app?

Thanks for any insights. There&#39;s nothing informative out there on ol&#39; WWW.

What happens in the case of app update. The local and web storage will get deleted or will it stay?


How permanent is local storage on Android and iOS?

How fast is looking up a value in localStorage with Javascript? 

Does anyone have links to any performance tests that indicate whether or not it is worth caching the data in a JavaScript object? Or does the browser already cache values that are accessed from localStorage anyway?

I am particularly interested in Firefox and Chrome implementations of localStorage.

Speed/cost of localStorage

Is there any limit (up to the amount of local storage available) for the key when using localStorage?

i.e. can I do something like:

    localStorage.setItem(&quot;pretend that this is a 1MB string&quot;, &quot;whatever&quot;); 



Is there a limit to the key length for localStorage?

I&#39;m just wondering how to get all key values in `localStorage`.


----------


I have tried to retrieve the values with a simple JavaScript loop

    for (var i=1; i &lt;= localStorage.length; i++)  {
	   alert(localStorage.getItem(i))
    }

But it works only if the keys are progressive numbers, starting at 1.


----------


How do I get all the keys, in order to display all available data?



Content Type	Original Author	Original Content on Stackoverflow
Question	Alex Churchill	View Question on Stackoverflow
Solution 1 - Google Chrome	Nathan Bubna	View Answer on Stackoverflow

Deleting from localStorage: should I use delete or .removeItem?

Google Chrome Problem Overview

Google Chrome Solutions

Solution 1 - Google Chrome

Why do we use _ in variable names?

Unobtrusive validation in Chrome won't validate with dd/mm/yyyy

Attributions