Tor Lillqvist b248787bfa We do want to temporarily use the idea that a "WASM app" is a separate thing ... Only once we have that working will we go back to having a COOL client that on the fly can switch from a normal COOL server to using local online and core code in WASM. Note that the --with-wasm-fallback configure option now then temporarily is a no-op, and the ENABLE_WASM_FALLBACK Automake conditional and WASM_BUILDDIR Autoconf macro are not used anywhere. Once we have something that barely works as a proof of concept, we can go back to working towards what we really want. (Yeah, yeah, I know that "temporary" solutions have a tendency to become more permanent than you expect...) Signed-off-by: Tor Lillqvist <tml@collabora.com> Change-Id: I2f01acd418686e672fd9d2e12cbbd688b128dfa5		2023-01-15 19:46:37 +01:00
..
Autolinker.js
global.js	We do want to temporarily use the idea that a "WASM app" is a separate thing	2023-01-15 19:46:37 +01:00
json2.js
l10n.js
ResizeObserverPolyfill.js
sanitize-url.js
select2.js
vex.combined.js	Don't use vex btn default btn CSS classes (rename)	2022-09-06 17:01:21 +02:00
viamapi-client.js
w2ui-1.5.rc1.js	Add outline to color indicator for classic mode	2022-08-16 15:49:49 +02:00