This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Are there any extensions similar to TextArea Cache or Lazarus Form Recovery which are multiprocess-(e10s)-compatible?

  • 1 antwoord
  • 1 het hierdie probleem
  • 1 view
  • Laaste antwoord deur John99

more options

I've only found two extensions which save text entered in form fields in case of accidentally leaving the page; TextArea Cache and Lazarus Form Recovery. However, neither of these extensions are e10s-compatible, and neither are likely ever to be (they appear most likely abandonware at this point).

Are there any e10s-compatible alternatives to these?

I've only found two extensions which save text entered in form fields in case of accidentally leaving the page; TextArea Cache and Lazarus Form Recovery. However, neither of these extensions are e10s-compatible, and neither are likely ever to be (they appear most likely abandonware at this point). Are there any e10s-compatible alternatives to these?

All Replies (1)

more options

They are the only two I am aware of. Lazarus does not seem to be under active development but TextArea Cache does still appear to be supported as it was updated in March 2016.

Have you installed Add-on Compatibility Reporter (ACR)

Unfortunately I have no idea how easy this fix may be, it may need a complete re-write of the extension, or it may not be possible in multi process mode to support such features. Developers will no doubt also be looking at what will be possible in the new WebExtensions and there again it may be waiting on new APIs before this can be implemented.

You could try posting in the add-ons forum but that is not a very active forum