obviously something is principially wrong, see attachment
tags as are recognized as invalid
any idea?
Additional info…
I did some further tests: It seems to be a browser issue (!)
the application starts well with firefox, chrome, edge whereas with IE11 the ui elements are not active, and the layout is completly different => not useable,
the issue can obviously be reduced to the netbeans “embedded browser”, workaround: don’t use it…
this has nothing to do with the tag warnings in the html files, they still appear as shown in the attached file
IE11 doesn’t support the modern ES6 syntax which is used in our client-side web components. To be able to run a Flow application on IE11, the ES6 code needs to be transpiled to older ES5 syntax, which is supported by IE11.
To do this, you just need to build the app in production mode, eg:
You got also warnings about HTML imports (<link rel="import">) in your code. HTML imports is also quite a new feature in the web and it’s not supported natively by many browsers. However, scripts called polyfills take care of making it possible to use this feature in browsers that don’t support it yet. Your application serves the polyfills by default, so you don’t have to worry about that.
The requestAnimationFrame should be supported even by IE11. Did you get that message only with the NetBeans embedded browser? Maybe that browser is just too out-dated.
Hi Pekka,
since I never tried to run a V10 app and there was a mix of different errors, and by chance the embedded netbeans browser was set, first I believe to hat a general problem in running a v10 app. In most of the cases I use either chrome or firefox, if the IE issue can be solved by an additional installation, nice to know, especially for those who have to use the IE, due to enterprise standards or whatever.
I don’t care about the HTML warnings, if they don’t prevent the app to by started, as it seems to be, nice to know too.
Eventually the embedded NB browser has also other limitations, normally I don’t really need it, and have just been confused by the error.
Maybe this browser specific limitation are also useful for other, who start with V10 coming from V8.
In my case with these addtional hint it’s fine.
Thank for your support
cu Pascal
I’m happy if I was able to clarify things for you.
If you want to build your application with HTML templates, I would suggest you to use an editor that supports these features.
Luckily V10 allows you to choose your workflow, so if you prefer building your application with Java components like in V8, it’s perfectly fine to not use the templates. Beverage Buddy is supposed to showcase most of the core features of V10, so it uses HTML template for one view and Java components for the other.
One more note about the production mode: As the name suggests, you should build your app in production mode only when it’s ready to be deployed for the users, so it will work even with IE11. Transpiling the files from ES6 to ES5 (and other optimizations that take place) takes a long time. When developing your app, you don’t want to wait for this process to finish every time you make changes to your code.
