Bug 1330966 - Add an ACCESSIBILITY guard around DocAccessibleParent usage in TabParent.cpp to fix --disable-accessibility bustage. r=dbolter
authorRyan VanderMeulen <ryanvm@gmail.com>
Fri, 13 Jan 2017 11:45:07 -0500
changeset 329319 83b1e97f352a360bd39442635ca0a963cc415ce0
parent 329318 e8b32aaa2eec84c15f44cfd677142a0047481152
child 329320 a60d62c55e27f7f62666d0215e3e818bc7f1430e
push id85680
push userryanvm@gmail.com
push dateFri, 13 Jan 2017 17:13:00 +0000
treeherdermozilla-inbound@f3ccf0f50160 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdbolter
bugs1330966
milestone53.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1330966 - Add an ACCESSIBILITY guard around DocAccessibleParent usage in TabParent.cpp to fix --disable-accessibility bustage. r=dbolter
dom/ipc/TabParent.cpp
--- a/dom/ipc/TabParent.cpp
+++ b/dom/ipc/TabParent.cpp
@@ -354,19 +354,21 @@ TabParent::IsVisible() const
 
 void
 TabParent::DestroyInternal()
 {
   IMEStateManager::OnTabParentDestroying(this);
 
   RemoveWindowListeners();
 
+#ifdef ACCESSIBILITY
   if (a11y::DocAccessibleParent* tabDoc = GetTopLevelDocAccessible()) {
     tabDoc->Destroy();
   }
+#endif
 
   // If this fails, it's most likely due to a content-process crash,
   // and auto-cleanup will kick in.  Otherwise, the child side will
   // destroy itself and send back __delete__().
   Unused << SendDestroy();
 
   if (RenderFrameParent* frame = GetRenderFrame()) {
     RemoveTabParentFromTable(frame->GetLayersId());