Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

pdf object postMessage not working in FF 22

  • 1 Antwort
  • 4 haben dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von Microrobot

newindian
newindian
more options

Hi,

After updating my FF to 22, i seen pdf object postMessage function does not working. We used adbove livecycle intraactive pdf forms to collect the data from the user.

When user click the save button from the pdf, postMessage function called, but after update this not getting execute.

For your reference i include the URL which also had the same problem. I also tried without addons.

Refer: http://www.windjack.com/WindJack/Browser2PDF/brwsr2acroJS.htm

HTML to PDF => works PDF to HTML => not working (in earlier versions it worked)

Thanks n Regards Mathan

Hi, After updating my FF to 22, i seen pdf object postMessage function does not working. We used adbove livecycle intraactive pdf forms to collect the data from the user. When user click the save button from the pdf, postMessage function called, but after update this not getting execute. For your reference i include the URL which also had the same problem. I also tried without addons. Refer: http://www.windjack.com/WindJack/Browser2PDF/brwsr2acroJS.htm HTML to PDF => works PDF to HTML => not working (in earlier versions it worked) Thanks n Regards Mathan

Alle Antworten (1)

Microrobot
Microrobot
more options

This is likely the fault of Livecycle Interactive. Most likely, Adobe has not yet provided an update for supporting Firefox 22. I would recommend informing adobe support about it.