Skip to content
Commits on Oct 19, 2010
  1. @mykmelez

    update version for next release

    mykmelez committed
Commits on Oct 18, 2010
  1. @mykmelez

    merge for backing out of changeset d1b2b899440d, the first of two com…

    mykmelez committed
    …mits for bug 598980, because it generates test failures per bug 604801 that are 0.9 release blockers
  2. @mykmelez

    back out changeset d1b2b899440d, the first of two commits for bug 598…

    mykmelez committed
    …980, because it generates test failures per bug 604801 that are 0.9 release blockers
  3. @mykmelez

    merge for backing out of changeset 680248df0349, the second of two co…

    mykmelez committed
    …mmits for bug 598980, because it generates test failures per bug 604801 that are 0.9 release blockers
  4. @mykmelez

    back out changeset 680248df0349, the second of two commits for bug 59…

    mykmelez committed
    …8980, because it generates test failures per bug 604801 that are 0.9 release blockers
Commits on Oct 17, 2010
  1. @mykmelez
Commits on Oct 13, 2010
  1. @Gozala

    Bug 592821 - update Private Browsing API for forwards-compatibility w…

    Gozala committed
    …ith electrolysis (r=adw)
  2. @warner

    Bug 591525: check require() paths against manifest generated at link-…

    warner committed
    …time
    
    The general idea is to put expected linker behavior in the machine-readable
    manifest, so that code-review tools can show a (human) reviewer what each
    require("foo") statement is expected to load, and then the runtime code will
    make sure that the expectations are met. This is intended to protect against
    an attack in which the XPI is modified, after the manifest is generated, to
    include a new module that the runtime linker will load in lieu of a module
    that the manifest specified, thus violating the reviewer's expectations.
    
    The manifest is now indexed by the resource: URL of the module being scanned,
    and is a regular dictionary/object rather than a hard-to-scan list. It also
    records more information about each module, including a hash of its contents,
    which can eventually be checked by the runtime linker.
  3. @Gozala

    Bug 603911 - Throw TypeErrors on assignment to read-only properties a…

    Gozala committed
    …nd test only custom ES5 functions
  4. @mykmelez

    bug 597004: fix test failures, for tests that use Iterator, due to ch…

    mykmelez committed
    …anges in content of strack trace, which we were using to detect Iterator usage; r=atul
  5. @Gozala
  6. @Gozala
  7. @mykmelez

    bug 603914: update test-traceback tests for changes to stack traces d…

    mykmelez committed
    …ue to slow-native removal; r=toolness
  8. @0c0w3
  9. @0c0w3
  10. @0c0w3
  11. @0c0w3
  12. @0c0w3
Commits on Oct 12, 2010
  1. @0c0w3

    Land bug 602460, which was landed in mozmill 1.5.1, to work around th…

    0c0w3 committed
    …at problem until we update mozrunner. r=atul
  2. @Gozala
Commits on Oct 11, 2010
  1. @0c0w3
  2. @0c0w3

    Use Windows-friendly string escapes in --static-args doc. (Works in b…

    0c0w3 committed
    …ash too.) Trivial doc fix, so r=me
Commits on Oct 9, 2010
  1. @0c0w3
  2. @0c0w3
  3. @0c0w3

    Bug 602688 - Liberate URLRule (match patterns) from page-mod module (…

    0c0w3 committed
    …part 2, page-mod changes). r=myk
  4. @0c0w3

    Bug 602688 - Liberate URLRule (match patterns) from page-mod module (…

    0c0w3 committed
    …part 1, match-pattern). r=myk
Commits on Oct 8, 2010
  1. @Gozala
  2. @Gozala

    change "windows" module to use `EventEmitter` event registration mode…

    Gozala committed
    …l and mergin with a work for side-bar (r=avarma)
  3. @Gozala
  4. @Gozala
Commits on Oct 7, 2010
  1. @0c0w3
  2. @0c0w3
Commits on Oct 6, 2010
  1. @Gozala
  2. @Gozala
Commits on Oct 5, 2010
  1. @toolness

    Bug 596092 - Get rid of the 'misc' root dir and create a 'bin/integra…

    toolness committed
    …tion-scripts' dir (r=warner)
Something went wrong with that request. Please try again.