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

Unified Diff: third_party/WebKit/Source/modules/accessibility/AXTableCell.cpp

Issue 2393003002: reflow comments in modules/accessiblity (Closed)
Patch Set: 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/modules/accessibility/AXTableCell.cpp
diff --git a/third_party/WebKit/Source/modules/accessibility/AXTableCell.cpp b/third_party/WebKit/Source/modules/accessibility/AXTableCell.cpp
index 0d521db6f19238b53b4ed2161039e00d25cc901f..4880b6f1f6fc1c462ffada39467a276e4e2b434e 100644
--- a/third_party/WebKit/Source/modules/accessibility/AXTableCell.cpp
+++ b/third_party/WebKit/Source/modules/accessibility/AXTableCell.cpp
@@ -84,10 +84,11 @@ AXObject* AXTableCell::parentTable() const {
if (isDetached())
return 0;
- // Do not use getOrCreate. parentTable() can be called while the layout tree is being modified
- // by javascript, and creating a table element may try to access the layout tree while in a bad state.
- // By using only get() implies that the AXTable must be created before AXTableCells. This should
- // always be the case when AT clients access a table.
+ // Do not use getOrCreate. parentTable() can be called while the layout tree
+ // is being modified by javascript, and creating a table element may try to
+ // access the layout tree while in a bad state. By using only get() implies
+ // that the AXTable must be created before AXTableCells. This should always be
+ // the case when AT clients access a table.
// https://bugs.webkit.org/show_bug.cgi?id=42652
return axObjectCache().get(toLayoutTableCell(m_layoutObject)->table());
}
@@ -159,7 +160,8 @@ void AXTableCell::rowIndexRange(std::pair<unsigned, unsigned>& rowRange) {
rowRange.first = layoutCell->rowIndex();
rowRange.second = layoutCell->rowSpan();
- // since our table might have multiple sections, we have to offset our row appropriately
+ // Since our table might have multiple sections, we have to offset our row
+ // appropriately.
LayoutTableSection* section = layoutCell->section();
LayoutTable* table = layoutCell->table();
if (!table || !section)

Powered by Google App Engine
This is Rietveld 408576698