Discussion  - 
Android Kitkat launch date may be revealed sooner by Google than their official announcement.
I just made an interesting find. The JavaScript code included in the android.com/kitkat/ page indicates that there will be added a "coming-soon countdown".

More specifically, there will be some invisible HTML elements added to the page source code even before the countdown will be visible. These elements should have the classnames "comingsoon-countdown" and "comingsoon-launched" and have "data-date" and "data-time" attributes containing the actual Android Kitkat launch date! They should look somewhat like this:

<div class="comingsoon-countdown" data-date="2013-10-28" data-time="12:30" style="display:none;">Super duper announcement</div>

So, have a close look at the source code of android.com/kitkat/ !

Edit (10/16): Oh Christ, I just saw from the reshares that some seem to misunderstand. The first screenshot is from my local code snippet that I used to "decompile" the original JS and how all works together. The values in the data-date and data-time attributes are fictive! The strings that will be added to the Android website will look like this, but not have exact the same values (unless my guess is correct ;-)).

Edit 2 (10/16): Thanks to +Jason Su , who cleared this up. As you can see from this pastebin http://pastebin.com/vmNcfTbS (a copy of the australian android web page) unfortunately the CSS class names and JS function probably refer to the start of the contest only.  

Edit 3 (10/17): Since this story was re-posted by a bunch of blogs (including phandroid.com, phonearena.com, androidheadlines.com, and androidspin.com) and there's still quite some buzz around it, let me quickly explain what it was all about (to get this finally clear).

The JavaScript file http://www.android.com/kitkat/js/kitkat.min.js and the CSS file http://www.android.com/kitkat/css/main.css are exact the same static resources for all locale versions of the Kitkat landing page. This is where I found the references to the coming soon countdown timer. 

Now, neither the default version of the Kitkat landing page (http://www.android.com/kitkat/index.html?hl=en ) nor most of the localized versions (eg. http://www.android.com/kitkat/index.html?hl=de, http://www.android.com/kitkat/index.html?hl=fr etc.) contain such HTML elements as I found references in the global kitkat.min.js and main.css.

So, because I found no such HTML elements, but the JS/CSS references to a countdown timer, and we're all waiting for the actual OS launch, my guess was that this (JS/CSS) code is for future use.

Later, someone in the comments pointed me to a cached copy of the ausralian website version. Only then I saw the (old) HTML code for the contest to win a Nexus 7 (btw, the russian version still has it: http://www.android.com/kitkat/index.html?hl=ru ) and that the JS/CSS references, that I stumpled upon, were obviously not for future use but that it was rather used in the past. 

To sum up: Found JS/CSS references to a countdown timer on the Kitkat page. > However, I did not found such HTML elements (as referenced) in the Kitkat page's source code. > We are all waiting for the Kitkat OS launch. > Of course, my first guess was that the countdown timer is related to the upcoming OS launch. And, I think, that was reasonable. And worth a share.

And to be perfectly honest: I've read much less reasonable #androidkitkatnexus5holomolyshutupandtakemymoney posts in the last days. ;-)

#androidkitkat #android44  
Stephan Schmitz's profile photoKevin Patton (KP)'s profile photoStuart Crabtree's profile photoGreg Hesp's profile photo
Next to Halloween I see. I sure hope its official so I can get my grubby hands on the new Nexus 5 :)
😭coming soon。。。。
you know that people wanna know a date when they check through the webpages source code after a date :)
+Yi-Ming Huang This is my guess, yep. The HTML elements are not visible by default (via CSS display:none). Then, the JS code checks whether the current datetime is greater or equals the date/time values given in the data-date / data-time attributes. If so, the elements will be set to be visible. In turn, I guess, the elements may be in the actual source code before the date when they should be visible on the web site.

Edit: However, it might be the case that Google will announce an event and the countdown will refer to this event - and not the actual launch. I just stumpled upon and found it worth a share.
So in plain English, does this mean the countdown begins on the 28th, or will it lead up to it?
+Stephan Schmitz I think this might just be referencing the contest start. Some versions of this page in other languages still have the divs lying around and they generally point to a date in September. For example,
the Australian version: http://pastebin.com/vmNcfTbS 
+Jason Su Thanks for the link. This sheds some light on these code parts. The pastebin code looks much like that's what it's refers to. :(
I think I might agree with +Jason Su.  No such code exists on the UK version of the page
So, I'm assuming here's what you found. A countdown timer will some day pop up. The dates and times you added are your examples only. Am I right?
+Derek Ross As stated in edit #1, yep. 

Updated the post with edit #2 - most likely this refers to the contest start only. :(
+Greg Hesp Neither does it exist in the US and german version. Otherwise I wouldn't have posted. ;-)
HEy whre ist the Div in the html code?

<div class="comingsoon-countdown" data-date="2013-10-28" data-time="12:30" style="display:none;">

Antwort gerne auch auf deutsch ;)
+Michael Stavrochristou See edit #1 - this exact line was meant as an example how the HTML elements should look like.  (In german: Siehe edit #1 - diese Zeile war lediglich ein Beispiel wie die HTML Elemente aussehen.)
If it's JS, is it using your local system clock?  Did you try setting your local time and date ahead to then and see what comes up?
Calm down Dan Brown. It'll be released when Goggle deems it ready.
This was also hidden in the CSS:
.nexushidden  {
 display: none !important;

  display: none;

  display: none;
  font-family: 'Open Sans', sans-serif;
  font-weight: 400;
  font-size: 17px;
  color: #555555;

  display: none !important;

Obviously the CSS for whatever they'll put in, and no, changing display doesn't work as the content doesn't exist yet.
Add a comment...