It's very late to the party ... So I wanted to contribute to my conclusions, each of which is associated with using $("#sigDiv").jSignature('getData', 'putSomethignInHere') function to verify the signature.
Here are the parameters that I examined for the second attribute passed to the jSignature function:
native returns an object object .length == 0 when the sig field is empty, and .length > 0 when there is something in the sig field. If you want to know how many strokes only the length of this object uses. NOTE. According to jSignature documentation:
"Stroke = mousedown + mousemoved * n (+ mouseup, but we donβt record that it was an end / no movement indicator)"
base30 also returns an object. Here I looked at the information in the second index position of this object. x = $("#sigDiv").jSignature('getData', 'base30')[1].length > 0 ? TRUE : FALSE x = $("#sigDiv").jSignature('getData', 'base30')[1].length > 0 ? TRUE : FALSE Here x will be TRUE if the field was signed, and FALSE when the jSig field is left untouched.
In my case, I used the base30 attribute to verify the signature , not just "did the user do something?" x = $("#sigDiv").jSignature('getData', 'base30')[1].length > {insertValueHere} ? TRUE : FALSE x = $("#sigDiv").jSignature('getData', 'base30')[1].length > {insertValueHere} ? TRUE : FALSE . To check if the user is really subscribed to the field and gave more than just ".". small "x". The return value of the second index received from base30 becomes more like complexity. Thus, if the user really only entered the point, x = $("#sigDiv").jSignature('getData', 'base30')[1].length will be about 5. The resulting value just gets bigger and bigger the bigger user draws in a field. The highest length that I recorded during my testing was 2272. And I scratched and scratched in the box for all 15 seconds.
According to jSig documentation:
base30 (alias image / jSignature; base30) (EXPORT AND IMPORT format) (VECTOR) is a compression format supported by base 64, configured for absurd compactness and native url compatibility. This is a "native" data structure, compressed into a compact string representation of all vectors.
image is a choice that I would avoid to check. It creates an object with a long string in the second index position. The last thing I measured was 672 characters. Using image creates a string regardless of whether the sig field is empty or in use. And to make things more impractical, the line created is different for the empty signature field in Chrome styles by the empty signature style in FF Developer. I am sure that the value of image used, but just not verified.
svgbase64 - this is similar to image with exceptions. Unlike image , using svgbase64 yields a longer, shorter string in second position. Also, this line is the same when I ran the Chrome FF Developer check. Here I stopped my testing. Therefore, I assume that you can use svgbase64 for verification.
These are my conclusions, yours may differ. Please do not hold my low reputation against me.