Hi Alex, here [1] seems to have at the end some proposal solution.
As you say maybe this is not urgent, since I didn't have in mind that production is minified and all in one file... Maybe we can to try some solution when we have more time, so we can defer for now. [1] https://blog.dareboost.com/en/2016/09/avoid-using-document-write-scripts-injection/ El mar., 16 oct. 2018 a las 18:22, Alex Harui (<[email protected]>) escribió: > I haven't tried Chrome. Did you look to see if there is a discussion > somewhere on the internet on how to address this? Or maybe it doesn't > matter as the production version probably doesn't write scripts. > > -Alex > > On 10/16/18, 2:40 AM, "Carlos Rovira" <[email protected]> wrote: > > Hi, > > when running whatever Apache Royale app in debug mode I get multiple > traces > like this: > > base.js:1167 [Violation] Avoid using document.write(). > goog.writeScriptSrcNode_ @ base.js:1167 > goog.writeScriptTag_ @ base.js:1241 > goog.importScript_ @ base.js:951 > (anonymous) @ base.js:1426 > > base.js:1167 [Violation] Parser was blocked due to > document.write(<script>) > goog.writeScriptSrcNode_ @ base.js:1167 > goog.writeScriptTag_ @ base.js:1241 > goog.importScript_ @ base.js:951 > (anonymous) @ base.js:1426 > > base.js:1167 [Violation] Parser was blocked due to > document.write(<script>) > goog.writeScriptSrcNode_ @ base.js:1167 > goog.writeScriptTag_ @ base.js:1241 > goog.importScript_ @ base.js:951 > (anonymous) @ base.js:1426 > > ... > > The app just works, but I was thinking if this could easily fixed or is > something we must live with it > > thanks > > -- > Carlos Rovira > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C3f5bd18d84784afb101308d6334b5f17%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636752796159337143&sdata=pZbTB2%2Bha9ZeMtTicfCnW%2FCKMSST1jnCfQCA%2FQYpWA4%3D&reserved=0 > > > -- Carlos Rovira http://about.me/carlosrovira
