Bug 1896047 part 1: Enclose TreeWalker implementation in a namespace block. r=eeejay

Without this, a new source file introduced in a subsequent patch causes the compiler to become confused about which TreeWalker we mean: a11y::TreeWalker or dom::TreeWalker.
I don't really understand why this starts happening, but I'm guessing it is related to our unified builds.

Differential Revision: https://phabricator.services.mozilla.com/D210013
This commit is contained in:
James Teh 2024-05-17 00:24:14 +00:00
parent 079607cbdc
commit a157ee3a80

View File

@ -11,8 +11,7 @@
#include "mozilla/dom/ChildIterator.h"
#include "mozilla/dom/Element.h"
using namespace mozilla;
using namespace mozilla::a11y;
namespace mozilla::a11y {
////////////////////////////////////////////////////////////////////////////////
// TreeWalker
@ -346,3 +345,5 @@ dom::AllChildrenIterator* TreeWalker::PopState() {
mStateStack.RemoveLastElement();
return mStateStack.IsEmpty() ? nullptr : &mStateStack.LastElement();
}
} // namespace mozilla::a11y