Its a design decision of
ftd and therefore
fpm to be UI engine agnostic.
ftd targets Web Browser by compiling to HTML/CSS/JS we want
to eventually create
ftd renderer that can target terminals, mobile
applications, PDF, low level canvas only surfaces, maybe even embedded devices.
We have taken a lot of inspiration from CSS, but we are not going to make CSS a
dependency. An FTD file generated on any UI engine (eg Browser) must work on
any other UI engine (within reason, eg terminal can not show things as richly as
Browser can). Because of these reasons, if you really want to use JS/CSS due to
your requirements, it’s better to not use