mailing list to dicuss incorporating es-libraries into UA?
is there a mailing list to discuss how, when and which scripts are
incorporated into UA?
why for instance text input via forms is in html, but not available**
to svg?
and looking slightly further ahead, there is a whole variety of high
level language such as game interaction that might also be embedded,
but currently relies on es-libraries.
cheers
Jonathan Chetwynd
**at spec. time xforms was planned, but a decade later not generally
implemented.
the result is es-workarounds are lengthy, buggy, ugly and hard to
maintain,
whilst the code is already embedded in the UA.
mailing list to dicuss incorporating es-libraries into UA?
is there a mailing list to discuss how, when and which scripts are
incorporated into UA?
why for instance text input via forms is in html, but not available**
to svg?
and looking slightly further ahead, there is a whole variety of high
level language such as game interaction that might also be embedded,
but currently relies on es-libraries.
cheers
Jonathan Chetwynd
**at spec. time xforms was planned, but a decade later not generally
implemented.
the result is es-workarounds are lengthy, buggy, ugly and hard to
maintain,
whilst the code is already embedded in the UA.
mailing list to dicuss incorporating es-libraries into UA?
is there a mailing list to discuss how, when and which scripts are
incorporated into UA?
why for instance text input via forms is in html, but not available**
to svg?
and looking slightly further ahead, there is a whole variety of high
level language such as game interaction that might also be embedded, but currently relies on es-libraries.
cheers
Jonathan Chetwynd
**at spec. time xforms was planned, but a decade later not generally
implemented. the result is es-workarounds are lengthy, buggy, ugly and hard to
maintain, whilst the code is already embedded in the UA.