Notice the answer from olton on github that AFAIK seems to prove that the issue is not in Metro4: that is triggering the change function on the input.


I've also replied that using addEventListener (what WebSharper is doing) seems to require a dispatchEvent, not just a trigger('change') (see the above thread on github for more details)


Bug will be fixed in the next release of Metro, in the meantime I've appied the above said dispatchEvent workaround to my local version of the script.

By on 7/24/2019 5:04 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper