Chris Dance

Agree. Options are good. I looked at this when the rescan event was added and there seemed like there where n different ways of defining these in a jQuery plugin...

I've taken a further look at this. It looks like the most popular "method" (no pun intended :-) is to pass strings into the constructor. e.g. ``` javascript $('#myform').areYouSure('rescan'); $('#myform').areYouSure('checkform');...

That's a great reference. Thanks for doing the investigation. The only more elegant solution I can come up with would be to maybe have a configuration option that can be...

That's good information. Would you be willing to submit a demo page to the repo? I'm thinking an example HTML file located at: ~demo/integration/ckeditor-ays-example.html Just a simple page that demonstrates...

Hi @DasaradhiR It should work fine with text boxes and text areas. Are you able to provide me with some sample HTML/JS that demonstrates the issues?

Hi Nikmauro, You may need to trigger are-you-sure to perform a manual check for change. Issue #17 and #62 provide some examples. https://github.com/codedance/jquery.AreYouSure/issues/17 https://github.com/codedance/jquery.AreYouSure/issues/62 Hope this helps.

I'd like to better understand the use-cases. It would be pretty easy to add a new class to the dirty field. It will add a bit of extra code complexity...

I think the request/ideas are valid and should be considered for inclusion. Here are the options as I see it: **Option 1)** Add a non-default option to mark dirty field...

Hi @anup36 . Are you able to provide an example page demonstrating the issue? e.g. a public URL test page, or codepen etc?

Is this related to the pull request #73 ? Did this change fix the issue?