2K9AXOt1E%2FPfeYc%3D&reserved=0>
From: Carlos Rovira
Sent: Wednesday, October 17, 2018 10:17:52 AM
To: dev@royale.apache.org
Subject: Re: Running debug Royale App in Google Chrome
Hi Alex,
I searched a bit about this but didn't foun
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 an
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 versi
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 version
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.co
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" wrote:
Hi,
when running whate
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 [
