Given an HTML template (say, MyTemplate) with bound input controls (say, A and B), instantiated on the server with initial values, currently yields default/empty values for those controls on the client. This is because these assignments happen on the server and they are not connected to the client-side initializer that executes upon page load. Consider the following example:
Here, upon page load, the client controls bound to A and B would be empty, instead of assuming the values given in the server-side code, making initializing view state without further handling more difficult than what it needs to be. This caveat is documented here under the "Mixing client code in server-side templates" subsection:
If you use ws-var="VarName", the corresponding Var will be created on the client on page startup.
However, passing a Var using .VarName(myVar) is not possible, since it would be a server-side Var.
This ticket aims to alleviate this shortcoming by providing the plumbing necessary to ship server-side template assignments to Vars to the client to execute on page load/initialization.
Given an HTML template (say,
MyTemplate
) with bound input controls (say,A
andB
), instantiated on the server with initial values, currently yields default/empty values for those controls on the client. This is because these assignments happen on the server and they are not connected to the client-side initializer that executes upon page load. Consider the following example:Here, upon page load, the client controls bound to
A
andB
would be empty, instead of assuming the values given in the server-side code, making initializing view state without further handling more difficult than what it needs to be. This caveat is documented here under the "Mixing client code in server-side templates" subsection:This ticket aims to alleviate this shortcoming by providing the plumbing necessary to ship server-side template assignments to
Var
s to the client to execute on page load/initialization.