JavaScript keyboard simulation in Google Docs

Other Questions Google docs
1

Hey everyone! I’m trying to figure out how to simulate keyboard input in Google Docs using JavaScript. I want to add or remove characters at the cursor position.

I’ve tried using keypress events, both with and without jQuery, but no luck so far. It seems Google Docs uses a virtual keyboard setup.

I found this function in their code:

VirtualInput.simulateKey = function(keyCode) {
  this.triggerEvent(new CustomEvent('input', {detail: {keyCode: keyCode}}))
};

Does anyone know how to properly trigger this event with JavaScript? Or are there other ways to simulate keyboard input in Google Docs?

I’m pretty stuck, so any help would be awesome. Thanks!

2

hey there! i’ve messed with this before. google docs is tricky. have u tried using the contenteditable attribute? might work better than key events. also, check out the mutation observer API. it can help track changes in the doc. good luck with ur project!

3

I’ve actually tackled a similar issue before when working on a browser extension. Google Docs’ security measures make direct keyboard simulation tricky. Instead of trying to simulate keystrokes, I found success by manipulating the document’s underlying content model directly.

Try exploring the Google Docs API. It provides methods to insert and delete text programmatically. While it requires some setup, it’s more reliable than attempting to simulate keyboard events.

Alternatively, you could investigate using the execCommand() method, though it’s deprecated. Something like document.execCommand(‘insertText’, false, ‘Your text here’) might work in some cases.

Remember, Google frequently updates their systems, so what works today might not tomorrow. Always test thoroughly and be prepared to adapt your approach.

4

I’ve actually encountered this challenge while developing a productivity tool for Google Docs. The VirtualInput.simulateKey function you found is internal and not easily accessible from external scripts. Instead, I’d recommend leveraging the Google Docs API for more reliable results.

In my experience, the API’s ‘insertText’ and ‘deleteContent’ methods work well for manipulating document content. You’ll need to set up OAuth2 authentication and use the appropriate API endpoints. It’s a bit more complex initially, but it’s far more stable and less likely to break with Google’s updates.

If you’re set on client-side manipulation, you might consider using MutationObserver to detect changes in the document’s structure, then inject your modifications accordingly. This approach requires careful handling of the DOM, but it can be effective for certain use cases.

Remember to thoroughly test your solution across different browsers and Google Docs versions. The landscape of web applications is always evolving, so staying adaptable is key.