Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of purplecabbage@gmail.com
 designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAzFgyiuaFJO+q69kW67==m-h6vWN5Jkn0vuoZhVuM+fEc=zjA@mail.gmail.com>
References: 
 <CAOBL_k6vmNtO19n5YEWzv2hneRw=btzOARq0e8sLKxXW6iQ08A@mail.gmail.com>
	<CABiQX1W8Fd+0qKwM4LpSFi96Wc6oG+50FQJru94spfncb02CuA@mail.gmail.com>
	<CAOBL_k45-12X2MmMS6zXFtb-L308UzYt_ri_FGOHOpahi3o27w@mail.gmail.com>
	<CAAzFgyiuaFJO+q69kW67==m-h6vWN5Jkn0vuoZhVuM+fEc=zjA@mail.gmail.com>
Date: Mon, 27 May 2013 12:25:30 -0700
Message-ID: 
 <CAKP6k2ujkT6m82=QNZO9zFNsgt1mMBYQ1naYY0WznP7N0SHUCw@mail.gmail.com>
Subject: Re: Changes in Mobile-Spec are breaking Cordova on Android 4.0.3 ICS
From: Jesse <purplecabbage@gmail.com>
To: Max Woghiren <maxw@chromium.org>
Cc: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=bcaec547c3ef97957e04ddb81c78

--bcaec547c3ef97957e04ddb81c78
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, there is a restriction against writing scripts with document.write in
Windows8 for Windows Store Apps.
+ I think that the proper way via createElement.
If you think it is better to just revert my change, that is fine, but I
think it points to another latent bug that is requiring a specific load
order, and we had/have an unknown race condition issue.
I will also look at alternatives.

Max, did reverting it fix it?


@purplecabbage
risingj.com


On Mon, May 27, 2013 at 11:04 AM, Max Woghiren <maxw@chromium.org> wrote:

> I'll take a look at whether reverting this change fixes the issue.  If so=
,
> I'll also wait for Jesse to chime in before doing anything else with it.
>
>
> On Mon, May 27, 2013 at 1:52 PM, Joe Bowser <bowserj@gmail.com> wrote:
>
>> I think it was made because document.write is ugly. That being said,
>> does this break something for WP? Seriously, adding a script tag
>> shouldn't cause the browser to not redraw, but I've seen stranger.
>>
>> On Mon, May 27, 2013 at 10:49 AM, Andrew Grieve <agrieve@chromium.org>
>> wrote:
>> > Might have been this change:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=3Dcordova-mobile-spec.git;a=3D=
blobdiff;f=3Dcordova-incl.js;h=3D458e10a7155d812d084720f7082c4aa1c63f44c8;h=
p=3Dc624996236eb2c7501714b48206c0b085460317a;hb=3D8b1fd7d49c278d43b34b4c041=
f1575a1a39a664d;hpb=3Dae18f3ea59d0b53880644ef8f8dcc3d0ade6f76d
>> >
>> > Maybe let's just revert it? Not sure why it was made in the first plac=
e?
>> >
>> >
>> > On Sun, May 26, 2013 at 7:55 PM, Joe Bowser <bowserj@gmail.com> wrote:
>> >
>> >> Hey
>> >>
>> >> While I was setting up my environment on the Chromebook for JSConf, I
>> >> noticed that I ran into the Android 4.0.3 bug again.  It seems that
>> >> when I was testing 4.0.3 last, I was using an old mobile-spec.  After
>> >> going through the project, it seems that the changes that were made t=
o
>> >> mobile-spec breaks rendering on Android.  I have no idea why this
>> >> would be, but this browser bug has nothing to do with the Android
>> >> changes, and is most likely something to do with the Android ICS
>> >> browser being a piece of crap.
>> >>
>> >> At any rate, can we get this fixed so that we can actually test this
>> >> release? What did we do to break mobile-spec on Ice Cream Sandwich?
>> >> Anyone have any ideas?
>> >>
>> >> Joe
>> >>
>>
>
>

--bcaec547c3ef97957e04ddb81c78--