On Fri, Jun 7, 2013 at 12:47 AM, <[email protected]> wrote: > > Comment #2 on issue 1757 by [email protected]: Date input types do not work > in ES5/3 > http://code.google.com/p/google-caja/issues/detail?id=1757 > > Look, as I guess is the case with 90% of bug reporters here, I’m actually > not that interested in caja itself. I’m just using the Google Apps Scripts’ > HtmlService to build user interfaces and that requires my code to go through > caja and since that one is obviously using the ES5/3 variant (or else it > would work), I reported this bug (which, in conjunction with bug #1636, > makes it difficult to build a date picker in an Apps Scripts UI dialog). So > if you’re deprecating the ES5/3 mode, does that mean HtmlService will switch > to the ES5 mode in the future?
Yes. > I have no idea what the cajoler is. Is that what you’re calling the server > component? Yes. > What is the designated replacement for that? There won't be a replacement. As the name suggests, ES5/3 is an emulation of EcmaScript 5 on top of EcmaScript 3. All modern browsers run ES5 natively, so there's no need for a serverside translation step. Getting the ES5 version of HtmlService deployed is their single most important goal. This rerating of the bug simply says they're not going to waste time doing anything other than fix the real root cause of the problem. -- Mike Stay - [email protected] http://www.cs.auckland.ac.nz/~mike http://reperiendi.wordpress.com -- --- You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
