javascript - Jquery Tooltipster with Validate - Warning? Non-standard document.all property was used -

-

i looking use jquery validate combined tooltipster in similar way example provided sparky on feb 7th '13: how display messages jquery validate plugin inside of tooltipster tooltips?

the difference being validation method via script function , not form submit. want attach tooltips class instead of whole form inputs. once validation complete function calls function.

it works shows following warning:

non-standard document.all property used. use w3c standard document.getelementbyid() instead.

which believe document.all deprecated , not existent in future browser versions. yet don't understand why code showing warning! have eliminated other possibilities of cause withing code. think either not seeing or tooltips + validation combined libraries causing warning.

here js code:

// initialize tooltipster on text input elements     $('.valid1').tooltipster({         trigger: 'custom',         onlyone: false,         position: 'right'     });      // initialize validate plugin on form     var validator = $('#propcreate').validate({     onsubmit: false,         errorplacement: function (error, element) {             $(element).tooltipster('update', $(error).text());             $(element).tooltipster('show');         },         success: function (label, element) {             $(element).tooltipster('hide');         },         rules: {              pkg: { required: true },             tcaccept: { required: true }          },         messages: {             tcaccept: "please check acceptance of our terms.",             pkg: "please select suitable package."         },         submithandler: function (form) {           }      }); //validation // validate terms checkbox & pkg $("#btnnext").click(function () {     if (validator.form()) {         btnnextcontinued()     } });

does have fix/workaround or can show me going wrong?

update : following great observation sparky , helpful comments - bug in firebug cause of false positive warning. tooltipster validate radio's , checkbox validation without form submit works fine @ time.

i'm not seeing reported non-standard document.all property warning message in of the demos.

is firebug date? i reading "non-standard document.all property" warning part of firebug bug , nothing more.

the more this, more seems non-issue.


Comments

Post a Comment

Popular posts from this blog

css - Which browser returns the correct result for getBoundingClientRect of an SVG element? -

-
this svg contains rect overflows svg element: <svg id='svg' width='10' height='10'> <rect x='-10' y='-10' width='30' height='30'/> </svg> chrome 28 , opera 12 return getboundingclientrect() svg element width , height of 10. firefox 23 reports width , height of 30. correct? jsfiddle the relevant spec cssom , delegates svg spec if svg element not "have associated css layout box". haven't found definition of "having associated css layout box", correct result seem hinge on definition, getbbox returns 30x30 rect in browsers. this firefox bug fixed now, fix in firefox nightlies , should make through firefox 33 released on 14 october 2014. see bug 530985 details.
Read more

gcc - Calling fftR4() in c from assembly -

-
i trying asm fft implementation www.embeddedsignals.com work. running make gives error: undefined reference fftr4(short*, short*, int) at top of asm have .syntax unified .thumb .global fftr4 .type fftr4, %function and there #define's associate c functions arguments registers followed macros fftr4 function uses. after that, fftr4 called .thumb_func fftr4: stmfd sp!, {r4-r11, lr} mov tmp0, #0 // bit reversed counter mov tmp1, #0 .word 0xf3a2fa92 //rbit r3,r2 //rbit r,n lsl r,#3 and c code follows: void fftr4(short *y, short *x, int n); short x[512]; short y[512]; int i; void loop() { (i=0;i<512;i++) x[i]=0; (i=0;i<512;i=i+8) { x[i+0]=16384; x[i+2]=16384; x[i+4]=-16384; x[i+6]=-16384;} fftr4(y, x, 256); serialusb.println(y[128]); serialusb.println(y[129]); serialusb.println(y[384]); serialusb.println(y[385]); // expected results: //y[128]is 8191; y[129] -8190 y[...
Read more

.htaccess - Matching full URL in RewriteCond -

-
i'm trying block post access site (and return 403), except 2 ip's , 1 url ( http://mydomain.com/about-us/contact-us/ ). here's have: rewritecond %{request_method} post rewritecond %{remote_addr} !=1.2.3.4 rewritecond %{remote_addr} !=4.3.2.1 rewritecond %{request_uri} !^http://mydomain.com/about-us/contact-us/$ rewriterule ^ / [f] these rules allowing access ip properly, contact page still not accessible. i'm not sure i'm using request_uri correctly? i've tried variations relative urls rewritecond %{request_uri} !^/about-us/contact-us$ , rewritecond %{request_uri} !^/about-us/contact-us/$ without luck. what doing wrong please? it looks me rule on file name specific. if relax bit, should work. made few other esthetic tweaks. give try: rewritecond %{request_method} post rewritecond %{remote_addr} !^1.2.3.4 rewritecond %{remote_addr} !^4.3.2.1 rewritecond %{request_uri} !about-us/contact-us rewriterule ^ - [f]
Read more