Bug 888256 - Adding support for speaking landmarks. r=eeejay, marcoz

---
 accessible/src/jsat/OutputGenerator.jsm            |   76 ++++++++--
 accessible/tests/mochitest/jsat/Makefile.in        |    1 +
 .../tests/mochitest/jsat/test_landmarks.html       |  154 ++++++++++++++++++++
 .../en-US/chrome/accessibility/AccessFu.properties |    8 +
 4 files changed, 225 insertions(+), 14 deletions(-)
 create mode 100644 accessible/tests/mochitest/jsat/test_landmarks.html
Bug 890279 - Create ScrollInfoLayers for frames we want APZC support. r=kats
Bug 890495. Add a reftest to test that dynamic changes to a legend element's margins are handled correctly.
Bug 891424. Directly remove nsCocoaWindow's from their parent in Destroy(). This allows us to stop implementing GetParent because the mac widget code has some assumptions about that always returning null. r=smichaud

This reverts implementing GetParent on nsCocoaWindow's (ie back out bug 869151) because the mac widget code has some assumptions about that. Instead we just remove nsCocoaWindow's from their mParent in Destroy() which will still keep bug 869151 fixed.
Bug 891469 - upload new talos.zip to build.mozilla.org to capture fixes for tscroll, tsvgx, tresize and datazilla uploading. r=armenzg
Bug 890179. r=seth a=abillings

--HG--
extra : rebase_source : f8c1f5adbdcc9bae652df901f256e8eac3fc5dc3
Bug 888607 - Correctly clear sub-frames. r=seth

--HG--
extra : rebase_source : 99ef0a24beea67613a67823fd35c313f933841c9
Bug 888607 - Test. r=seth

--HG--
extra : rebase_source : aeecfcc1c178f1a8402291fbeb698ca0c4b4d980
Bug 717872 - Move frame ownership to a separate container object, FrameSequence, which only exposes const access to its frames. r=seth

The eventual goal here is to have FrameBlenders be able to share
FrameSequences.

--HG--
extra : rebase_source : 97b8be9f53ed5cb14f0d46655d8fd7cdfa6bab67
Bug 717872 - Make FrameSequences be refcounted, and store a RefPtr to FrameSequence on FrameBlender. r=seth

This makes it possible for us to share FrameSequences by refcounting them. We
don't do anything smart when inserting/removing/swapping frames, but we do
carefully handle the "discard" case (by just reallocating a new
FrameSequence).

Note that, currently, nothing actually *shares* FrameSequences.

--HG--
extra : rebase_source : 9facdf8930297888f2ee77e0816543c6ad703f80