The Endpoint Agent is not compatible with Chrome at the present time, so you would not be able to see HTTPS traffic on sessions establised with the Chrome browser.
HTTPS monitoring at the Agent level is done through a plugin to the browser. The agent plugins only work on IE and Firefox.
HTTP monitoring, however, is done at the protocol level on the Endpoint, meaning it shouldn't matter what browser the end user is using. Google Docs happens to be HTTPS, so sessions establised using Chrome will not be monitored.
There are two options for HTTPS in the agent configuration, one for IE, one for Firefox. I'm presuming that both are enabled in your case. If not, then you need to enable the option for Firefox. Other things you might check are wheter or not the Agent on the machine(s) you are testing with have the current configuration. Also check to see if there are any Agent Events for the workstations you are working with that indicate that the plugin has been tampered with. Beyond that, you are probably going to need to go through some log collection and debugging exercises on the specific agents that you expect to be capturing this activity on. For one, make sure that the plugin for Firefox has been successfully installed on the workstation.
~Keith