Permalink
Switch branches/tags
Nothing to show
Commits on Oct 21, 2012
Commits on Oct 18, 2012
  1. Merge pull request #11 from Steffen185/patch-2

    gregersrygg committed Oct 18, 2012
    Bugfix
  2. Obvious bugfix

    steffenweber committed Oct 18, 2012
  3. Merge pull request #10 from Steffen185/patch-2

    gregersrygg committed Oct 18, 2012
    Ignore document.open() and document.close()
  4. Test-Case for Issue #10

    steffenweber committed Oct 18, 2012
Commits on Oct 17, 2012
  1. Ignore calls to document.open/close

    steffenweber committed Oct 17, 2012
    I have found an ad that calls document.open() and document.close(). This causes problems for crapLoader. Ignoring these calls solves the problem.
Commits on Oct 9, 2012
  1. Unit test for Issue #9

    gregersrygg committed Oct 9, 2012
  2. Merge pull request #9 from Steffen185/patch-1

    gregersrygg committed Oct 9, 2012
    traverseForElById: Fix for buggy DFS
  3. traverseForElById: Fix for buggy DFS

    steffenweber committed Oct 9, 2012
    The depth-first search in traverseForElById has a bug: If node A has a first child then A's siblings are never considered.
    
    A test-case that fails without this bugfix: 
    
    document.write('<div><img/></div><div id="myDIV"></div>');
    document.getElementById('myDIV').innerHTML = 'Works';
Commits on Oct 7, 2012
  1. More unit tests

    gregersrygg committed Oct 7, 2012
  2. Removed a console.log

    gregersrygg committed Oct 7, 2012
Commits on Oct 6, 2012
  1. We are evil

    gregersrygg committed Oct 6, 2012
  2. Merge pull request #8 from colinux/get-element-by-id-twice

    gregersrygg committed Oct 6, 2012
    Fixed case when a same element is searched twice by getElementById()
Commits on Sep 23, 2012
  1. Fixed case when ajax or whatever update dom fragments with the same i…

    colinux committed Sep 23, 2012
    …ds as before
    
    If in the updated fragment an id was used as target by crapLoader before
    the request, then the new element with the same id used as target too
    would not be updated by crapLoader, because the first element with this id still
    existed in `elementCached`.
    So we need to flush this cache when crapLoader enters in "release" mode.
Commits on Sep 22, 2012
  1. Fixed case when a same element is searched twice by getElementById()

    colinux committed Sep 22, 2012
    If the element was created in buffer, we need to return the second time
    the same element as the first time because it could have been modified
    (attributes, new childs etc...)
Commits on Jun 13, 2012