function(value, element) on mapped field - has behavior changed in last build?

[John5269257]

I have functions in the 'add js' section of mapped fields that were working fine the day before yesterday but are now returning the element as undefined. Old versions of the site still work fine, but testing the app in appery fails.

as a test, for example just putting:
element.addClass("newclass") ;
in the javascript of a mapped field returns an error that element is undefined, and yet the value has been updated by the service.

What's changed, and how do I deal with it?

Thanks,
John

[Maryna Brodina]

Hello! It's a known high priority bug. We'll fix it as soon as possible. Sorry for inconvenience.

[John5269257]

Marina, that's great - I can take the weekend off while you guys fix it! (5:15pm for me)

[Maryna Brodina]

bug is fixed already