Hallo Andy
Hier noch einige Info vom HTML - Debugger im FF, vielleicht bringen folgende "fett" markierten Punkte die Lösung:
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help
http://xhr.spec.whatwg.org/ ajax.js:16:0
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. 192.168.1.19
Iframe attached successfully content.js:4:21444
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help
http://xhr.spec.whatwg.org/ app.js:3:0
not well-formed indexed.json:1:1
not well-formed en-US.json:1:1
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help
http://xhr.spec.whatwg.org/ ajax.js:41:0
Use of XMLHttpRequest's timeout attribute is not supported in the synchronous mode in window context. ajax.js:42:0
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help
http://xhr.spec.whatwg.org/ ajax.js:16:0
not well-formed en-US.json:1:1
Use of XMLHttpRequest's timeout attribute is not supported in the synchronous mode in window context. ajax.js:42:0
Password fields present on an insecure (http://) page. This is a security risk that allows user login credentials to be stolen.[Learn More] <unknown>
Password fields present on an insecure (http://) iframe. This is a security risk that allows user login credentials to be stolen.[Learn More] <unknown>
Password fields present in a form with an insecure (http://) form action. This is a security risk that allows user login credentials to be stolen.[Learn More] <unknown>
TypeError: btn is null email.htm:1:36
A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element. email.htm
TypeError: btn is null email.htm:1:36
TypeError: btn is null email.htm:1:36
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help
http://xhr.spec.whatwg.org/
