Since you actually got the editor's contents to work correctly (which is amazeballs! :fireworks:), why not just keep `.content` in there, but here convert it to a friendly format like (instead of the `delete data[file].content line):

```js
data[file].content = self.exportFile(file);
```

I dont believe that actually replaces anything in localStorage, right? I looked back at some more code and I realized `.content` was often used for things like:

```js
var documentId = '123-45-67890'; // Set by the server on page load or 
editor.on('update', function (file) {
  $.ajax({
    type: 'POST',
    data: {
      id: documentId
      content: file.content
    }
  });
});
```

So, if you dont have any strong objections to removing `.content` in there now that it _seems_ fixed in all my tests, I'd love to keep it in there or else this update is going to be rough for some projects. They'll have to refactor all their event handlers and code a lot because the filename isn't passed back `getFiles(foo)`. You'd have to manually figure out what file is the currently open file.