Work on a dead simple tutorial on making Chrome extensions.
Did a tutorial on turning the password fields red
Completed an experiment to grab text from a text field after a user hits a button on a basic webpage.
I forgot to put my experiment in the experiments folder..... woops
Merge branch 'experiment_erik' of https://code.google.com/p/you-shall-not-pass into experiment_erik
Completed an experiment where I modified the plain text of a password field on submitting a password form.
Retooling the StoreInput experiment to use disk via the Google FileSystem API.  Updated manifest.
Merging master to my development branch so that I can see Mr. DeFrancia's and Mr. Devlin's extension samples.  I cannot seem to get the StoreInput extension to work the way I would expect an extension to work.
Adding an experiment which explores the relationship between the content script, the popup page, the browser's current tab, and the background page of the extension.  This experiment doesn't do much except turn password forms red.  Also, starting to develop better coding standards for the repository.  Namespaces please.  File comment headers please.
Took a look at Dr. Crenshaw's experiment.  It looked like the button on the form was not included in the form.  Triggering off the onsubmit event was causing problems, because when the from reloads it was not allowing a response from the background page.  I changed it to the onclick event and it seems to be happy as a clam. I also added a case where the greeting was WTF!?
Updated the TODO comment in storeSecrete.js
Small edits to comments so that the description of what the experiment does is up-to-date.
Create the Greystash extension and website.  Most files are empty.  The extension does nothing and the website is blank.  The password.js in the website is just a symbolic link to the password.js in the extension directory.
Rename extension.html to popup.html to make its purpose more clear.  Add popup.js to hold the Javascript logic for submitting an extension password from this popup.
Implement the browser action popup.  The popup sends the typed extension password to the background script.
Add some basic functionality to the extension.  Password fields are hilighted red when the page loads.  The submit button is also overridden, but simply logs the form to the console rather than doing anything with the password.
Began adding function headers to password.js
Add function stubs for password.js
OK I think this will be able to generate a fake from and submit it regardless of if we are changing a password or not. For submitting a form that has more than 1 password field, you have to send a click event, and not override submit
I made the code less grotesque in hopes that crenshaw will not punch me