Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(76)

Unified Diff: third_party/WebKit/Source/core/html/parser/HTMLElementStack.h

Issue 2386893002: Reformat comments in core/html/parser (Closed)
Patch Set: self review Created 4 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/Source/core/html/parser/HTMLElementStack.h
diff --git a/third_party/WebKit/Source/core/html/parser/HTMLElementStack.h b/third_party/WebKit/Source/core/html/parser/HTMLElementStack.h
index fa44f6af32b35f5018ede2bcbdb8dabcfb68a2e8..6dd6cc23e81d8b285254e62598859c9d4f3ac426 100644
--- a/third_party/WebKit/Source/core/html/parser/HTMLElementStack.h
+++ b/third_party/WebKit/Source/core/html/parser/HTMLElementStack.h
@@ -119,12 +119,16 @@ class HTMLElementStack {
void popUntilPopped(Element*);
void popUntilNumberedHeaderElementPopped();
- void
- popUntilTableScopeMarker(); // "clear the stack back to a table context" in the spec.
- void
- popUntilTableBodyScopeMarker(); // "clear the stack back to a table body context" in the spec.
- void
- popUntilTableRowScopeMarker(); // "clear the stack back to a table row context" in the spec.
+
+ // "clear the stack back to a table context" in the spec.
+ void popUntilTableScopeMarker();
+
+ // "clear the stack back to a table body context" in the spec.
+ void popUntilTableBodyScopeMarker();
+
+ // "clear the stack back to a table row context" in the spec.
+ void popUntilTableRowScopeMarker();
+
void popUntilForeignContentScopeMarker();
void popHTMLHeadElement();
void popHTMLBodyElement();
@@ -178,9 +182,9 @@ class HTMLElementStack {
// We remember the root node, <head> and <body> as they are pushed. Their
// ElementRecords keep them alive. The root node is never popped.
- // FIXME: We don't currently require type-specific information about
- // these elements so we haven't yet bothered to plumb the types all the
- // way down through createElement, etc.
+ // FIXME: We don't currently require type-specific information about these
+ // elements so we haven't yet bothered to plumb the types all the way down
+ // through createElement, etc.
Member<ContainerNode> m_rootNode;
Member<Element> m_headElement;
Member<Element> m_bodyElement;

Powered by Google App Engine
This is Rietveld 408576698