Clarify fullscreenElement vs. currentFullScreenElement distinction

third_party/WebKit/Source/core/dom/Element.cpp

Index: third_party/WebKit/Source/core/dom/Element.cpp
diff --git a/third_party/WebKit/Source/core/dom/Element.cpp b/third_party/WebKit/Source/core/dom/Element.cpp
index ef260adf32dc31fb8e8c0d0dfbfbde675c104369..6c4799678fb8945addc700ecdfa79c43e970bdad 100644
--- a/third_party/WebKit/Source/core/dom/Element.cpp
+++ b/third_party/WebKit/Source/core/dom/Element.cpp
@@ -1469,7 +1469,7 @@ void Element::removedFrom(ContainerNode* insertionPoint)
 
     DCHECK(!hasRareData() || !elementRareData()->hasPseudoElements());
 
-    if (Fullscreen::isActiveFullScreenElement(*this)) {
+    if (Fullscreen::isCurrentFullScreenElement(*this)) {
         setContainsFullScreenElementOnAncestorsCrossingFrameBoundaries(false);
         if (insertionPoint->isElementNode()) {
             toElement(insertionPoint)->setContainsFullScreenElement(false);
@@ -3697,7 +3697,7 @@ bool Element::supportsStyleSharing() const
         return false;
     if (hasAnimations())
         return false;
-    if (Fullscreen::isActiveFullScreenElement(*this))
+    if (Fullscreen::isCurrentFullScreenElement(*this))
         return false;
     return true;
 }