Cannot draw on signature pad if dynamically included from WebSocket onMessage event about signature_pad HOT 5 CLOSED

A few questions:

1. Does it work if you open the same page with signature pad HTML already in it (without it being sent via WebSockets) in Firefox on the same tablet with Windows 8?
2. Does it work if you append signature pad HTML using element.appendChild(child)?
3. Do you call new SignaturePad(canvas) after or before canvas element is appended to the page?

To sum it up - you've got an HTML page, receive signature pad HTML + JS via WebSockets, append received HTML to the page and the appended signature pad doesn't receive touch events?

from signature_pad.

Thanks for quick reply! Yes, saving the page served via WebSockets as a
file and reopening this file will allow to use signature pad as expected.

Your summary is correct, "append received HTML" meaning replacing the
contents of

from signature_pad.

I guess you're serving signature pad HTML together with JS code that initializes signature pad? Could you try to use setTimeout to delay calling new SignaturePad(canvas) for e.g. a second or so? The only idea I've got at the moment why it might not work is that touch event handlers are attached to canvas before canvas is appended to DOM.

from signature_pad.

Serving signature pad HTML together with script tag that includes your
app.js. Modified app.js to call new SignaturePad(canvas) like this:

setTimeout(function() {
signaturePad = new SignaturePad(canvas);
}, 2000);

but unfortunately no change.

On 12/29/13 07:48, Szymon Nowak wrote:

I guess you're serving signature pad HTML together with JS code that
initializes signature pad? Could you try to use |setTimeout| to delay
calling |new SignaturePad(canvas)| for e.g. a second or so? The only
idea I've got at the moment why it might not work is that touch event
handlers are attached to canvas before canvas is appended to DOM.

---

Reply to this email directly or view it on GitHub
#40 (comment).

from signature_pad.

OK - found my mistake, revealing the shallowness of my JS knowledge, I apologize.

When including the signature pad HTML, included all the new required JS simply via HTML script tags expecting it to execute like it would when serving the page as a complete standalone HTML page. But when including JS dynamically, one has to use eval or add a script tag with the script URL via JS (see http://stackoverflow.com/questions/950087/how-to-include-a-javascript-file-in-another-javascript-file). In my case it was enough to include signature_pad.js in the base HTML doc and inline app.js in the onMessage WebSocket function body.

So, signature pad is working nicely now as intended :-)

Thanks for your time and help and great script!

from signature_pad.