Here's the link. https://groups.google.com/forum/#!topic/clojure/ehrD0Bc89ek
-Alex On 10/17/18, 1:38 PM, "Alex Harui" <[email protected]> wrote: The output showed that the error is coming from base.js in Google closure library not the framework or compiler generated code. I found this forum post that implies that you are just supposed to ignore it during development since the production version won't have this problem. The post mentioned that there might be a way to suppress the output but it might suppress other things as well. Alex Get Outlook for Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%7C7b314d83c8704d57db2908d634707315%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636754054935034636&sdata=wgT%2FPs7GipJzvMjbAOLRv9%2B7bJvX2K9AXOt1E%2FPfeYc%3D&reserved=0> ________________________________ From: Carlos Rovira <[email protected]> Sent: Wednesday, October 17, 2018 10:17:52 AM To: [email protected] Subject: Re: Running debug Royale App in Google Chrome Hi Alex, I searched a bit about this but didn't found nothing important. Since I don't have the time right now for this, we can postpone to get over again as we have some free time. What I saw is that document.write() is greatly demonized and nobody wants to ear from it ;). So maybe some new version of GCL and GCC should avoid it, or maybe we're using it in out compiler code and we should refactor some of the recommended codes. Anyway, time to archive for now, and revisit at a later time... thanks Carlos El mar., 16 oct. 2018 a las 19:01, Alex Harui (<[email protected]>) escribió: > HI Carlos, > > That link explains why Google is generating warnings, but I was hoping you > would find a discussion about how users of Google Closure Library should > modify their code to get past this warning. I think the document write > calls are coming from GCL and not our code. Maybe newer versions of GCL > and GCC are needed or something like that. > > -Alex > > On 10/16/18, 9:43 AM, "Carlos Rovira" <[email protected]> wrote: > > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.dareboost.com%2Fen%2F2016%2F09%2Favoid-using-document-write-scripts-injection%2F&data=02%7C01%7Caharui%40adobe.com%7C7b314d83c8704d57db2908d634707315%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636754054935034636&sdata=Jz12wcSOk9QEDYigLFcGPVjT81xCD0cJyJDQ%2FROvU2U%3D&reserved=0 > > 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%7C7b314d83c8704d57db2908d634707315%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636754054935034636&sdata=42lRl8ETwYm8UBD5dCHL3xEKdl0fBZWYpBoKiANgOQc%3D&reserved=0 > > > > > > > > -- > Carlos Rovira > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7b314d83c8704d57db2908d634707315%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636754054935034636&sdata=42lRl8ETwYm8UBD5dCHL3xEKdl0fBZWYpBoKiANgOQc%3D&reserved=0 > > > -- Carlos Rovira https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C7b314d83c8704d57db2908d634707315%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636754054935034636&sdata=42lRl8ETwYm8UBD5dCHL3xEKdl0fBZWYpBoKiANgOQc%3D&reserved=0
