Bug 921454 - Allow chromeOnlyContent to work for non-chrome XBL documents. r=smaug

Given that we turn off XBL for the web, this just affects remote XUL/XBL, in
particular our tests. And it's expedient for NAC testing to be able to test
with an in-content XBL binding.
This commit is contained in:
Bobby Holley 2013-10-04 13:29:35 +02:00
Родитель 78d1f83d78
Коммит 169c6eab28
1 изменённых файлов: 1 добавлений и 2 удалений

Просмотреть файл

@ -208,8 +208,7 @@ nsXBLPrototypeBinding::SetBindingElement(nsIContent* aElement)
nsGkAtoms::_false, eCaseMatters)) nsGkAtoms::_false, eCaseMatters))
mInheritStyle = false; mInheritStyle = false;
mChromeOnlyContent = IsChrome() && mChromeOnlyContent = mBinding->AttrValueIs(kNameSpaceID_None,
mBinding->AttrValueIs(kNameSpaceID_None,
nsGkAtoms::chromeOnlyContent, nsGkAtoms::chromeOnlyContent,
nsGkAtoms::_true, eCaseMatters); nsGkAtoms::_true, eCaseMatters);
} }