Activity (RSS)

this is resolved in 1.0.x

this is working in our latest trunk

This has been changed. You can now modify all core DOM and HTML classes

i threw this check into our latest and the issue seems resolved

<script>
        function testXMLSpecialCharacters(){
            if(true && true && 0>-1){
   ...

Will try to get this fixed in the next couple of days. Thanks for reporting and sorry for the delay!

general relaxed parsing is being moved to 1.1

done see docs on new home page http://www.envjs.com/docs/api-1.0.x

done see

http://www.envjs.com/docs/

done

done!

duplicate of #38

This is fixed now ;)

it looks like this got fixed when we exposed core function prototypes for modification, eg Element

extra id is resolved and I believe extra space. looking into the treatment of the text node output we have to push this ticket to 1.1 as the unescaped xml chara...

again sorry for delay, adding this now. will be pushed out asap.

gosh Jonathan sorry for the tremendous delay. I got this in my local git and will push it out with a couple other small patches tomorrow

There is a very strong pragmatic argument for this feature. If you want to use env.js to do command line XML processing you want to be able to have the format o...

decided not to change this as neither xml nor html require double quotes

thanks for creating a ticket though. we'll add some unit tests for the window.location api to ensure it stays stable

going to mark this as invalid. moving to 1.1 i want the focus to be on a unified parser that is much looser and handles html tags and in-the-wild markup.

this was fixed by Glen E Ivey's frame contributions

this was corrected by making sure all strings are created with +'' in platform/rhino.js where java is being used directly.

sorry I'm finally getting to this. I never got to checking out the code, but i ran into this issue also when working with ajax posts. it should be corrected in ...

should have been marked closed awhile ago

(I apologize in advance in case I seem a bit lost, I haven't followed or played with EnvJS in a while)

First, I just realized I never mentioned this bug was for...

I think I fixed this (in a different way) in all of the changes I made to the scoping of window objects and frames. Also, note that even if the proposed change ...