Looks like shed loads of changes were done here, which includes the code
referenced in the error I saw...

https://github.com/pyjs/pyjs/commit/62bf5c19cbceebcaf873081af17d29e889286e2d

On Thu, Jun 28, 2012 at 12:50 PM, Phil Charlesworth <
jpcharleswo...@gmail.com> wrote:

> **
> On 28/06/12 09:28, Apexi 200sx wrote:
>
> Could someone check the latest GIT PYJS and see if they can build
> HelloWorld example app and have it work in browsers other than firefox
> please, then at least I know whether I have screwed something up or
> someone's commit broke it.
>
> On Wed, Jun 27, 2012 at 8:51 PM, Apexi 200sx <apexi.20...@gmail.com>wrote:
>
>> More info...
>>
>> """
>> Webpage error details
>>
>> User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1;
>> Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
>> 3.0.30729; Media Center PC 6.0; BRI/2)
>> Timestamp: Wed, 27 Jun 2012 19:46:57 UTC
>>
>>
>> Message: Expected ')'
>> Line: 18723
>> Char: 32
>> Code: 0
>> URI:
>> file:///D:/dev/pyjs_git/examples/helloworld/output/Hello.ie6.cache.html
>> """
>>
>>
>>
>>     ua = navigator['userAgent']['toLowerCase']();
>>     if (ua['indexOf']('msie 9['0']') != -1) {
>> <------------------------------- line 18723
>>         var elem = $doc['createElement']("INPUT");
>>         elem['type'] = 'radio';
>>         elem['name'] = group;
>>         return elem
>>
>>     }
>>
>> On Wed, Jun 27, 2012 at 5:57 PM, Apexi 200sx <apexi.20...@gmail.com>wrote:
>>
>>> Just done a fresh git clone of the repo
>>>
>>> Just done a pyjsbuild.bat on a couple of the example apps but I just get
>>> an error in IE, but the app displays fine in Firefox, not tried Chrome.
>>>
>>> See attached screenshot...
>>>
>>> Any ideas ?
>>>
>>        You should post this on the bug tracker. As far as I can see,
> none of the examples work on IE any more because the compiler is producing
> code with syntax errors. This must be the result of a very recent change -
> the IE6 code was always rock solid before.  I haven't time at the moment to
> try to track down the commit which caused this problem but it has happened
> since the new management took over.
> Phil
>
>
>>
>
>

Reply via email to