How to Save Work on Quora and Single Page Apps

Published: September 27, 2026. Updated: October 2026 by Andrew Apell, who builds Form ReDraft

Quick Answer

Short answer: Single page apps such as Quora swap the view without loading a new page, so there is no moment when the browser would save anything. A tool that saves each field on change survives it. It does not depend on the page being destroyed and rebuilt. Autofill based tools and recovery tricks do not.

Key Takeaways

  • Quora is the textbook case because it rebuilds the writing surface as you move between views. That is the exact behaviour that loses text nothing had copied.
  • The browser never owned the text, so nothing in its cache or history can return it. A tool that reads only the original page markup will never find the field at all.
  • Testing a tool on a single page app takes one reload. It separates the tools that work from the ones whose listings assume a plain form.

Quora comes up in reviews of form recovery tools more than any other site, and the complaint is always the same sentence in slightly different words. It works everywhere else and does nothing here. That is not Quora's fault and it is not a quirk. It is the clearest demonstration of a failure built into how modern sites render.

How the Old Approach Works

The classic recovery tool assumes a page lifecycle. A document loads, its fields exist in the markup, you type into them, and when you leave the page the browser either keeps it in the back-forward cache or discards it.

Everything in that model depends on there being a document with fields and a navigation that can be detected. A tool built for it hooks page loads, walks the form elements, reads their values and restores them when the document returns. On a site that behaves that way, the approach works well. That is why so many tools were built on it.

What a Single Page App Does Instead

A single page app loads one document and then replaces its contents as you navigate. The address bar changes, the screen changes, and no new document is created. There is no page load to hook and no navigation to detect.

Worse for the old model, the writing surface is often rebuilt on each view change. The element that held your text is removed and a fresh one inserted. Even a tool that found the field once would be holding a reference to something that no longer exists. The app is also free to generate new identifiers per render, which defeats any tool that tries to remember a field by its name or index.

Why Quora Is the Textbook Case

Quora combines the worst of both patterns. The answer composer is a rich text surface, not a textarea. It is remounted when you move between the question, the answer and the feed. It keeps a server side draft only once the platform has accepted something.

So the text lives in application memory, inside a component that can disappear, behind a draft that arrives late. Everything that would have to line up does not. The result is an empty box on a page that never navigated anywhere.

What Actually Fixes It

Two properties count, and a tool needs both. It has to capture on change rather than on unload, so a value is saved while you type instead of when the page goes away. It also has to restore through the interface the framework listens to, so the value enters the application's model rather than sitting in the element until the next render.

Form ReDraft is built that way. It writes a local encrypted copy shortly after you pause, then restores by dispatching the events a person typing would produce. Because the copy lives on your device, it also covers a case the app never did: closing the browser with an unsaved answer in progress.

How to Test Any Tool, Including This One

  1. Open a site you know is built as a single page app, ideally one that has lost text for you before.
  2. Type a distinctive sentence into the main writing surface, then click somewhere else inside the app so the view changes without a page load.
  3. Return to the composer, look for the restore affordance, accept it and wait five seconds for the app to re-render.
  4. If the text survives a re-render, the tool handles editors. If it appears and then vanishes, it is writing to the screen rather than into the app.

Run this before you trust any tool with an hour of work, and run it on the specific site that matters to you. A demo on a plain contact form proves nothing about the surface you actually write in.

If You Build Pages as Well

The same lesson applies in reverse. If your product holds user text in component state alone, you have designed a page that loses work on a route change, and no extension can fully compensate. Persisting a draft to storage on change and restoring it on mount takes a few lines of code. It is a better promise than any recovery tool can make on your behalf.

The technical detail for that restore is in how to restore text into React inputs, which covers why writing to the element alone is not enough.

FAQ

Why does no extension work on Quora?

The answer box renders as a rich text surface inside a component that re-renders often, and the surrounding fields change identifier on every render. A tool that looked once, on load, for named fields never sees it.

How do I test whether a tool supports single page apps?

Type into a field, navigate to another screen within the same site using its own navigation, then come back. If the tool offers your text, it re-checks the page instead of reading it only once.

Why do some fields get new ids on every render?

Component frameworks often generate unique identifiers to keep list items distinct. On a form screen it is unnecessary, but it is cheap, so it happens often and quietly.

Can a page have stable field identifiers at all?

Yes. Give every input an id, associate it with a label and the problem disappears. It is a small accessibility improvement that also makes automation possible.

Made for the Sites Other Tools Struggle With

Form ReDraft watches pages continuously, walks into shadow roots, checks again after every route change and falls back to matching on the field label.

Read the documentation
Project Slidecut