Classification of TODOs in Panel code.

chrome/browser/ui/panels/base_panel_browser_test.cc

Index: chrome/browser/ui/panels/base_panel_browser_test.cc
diff --git a/chrome/browser/ui/panels/base_panel_browser_test.cc b/chrome/browser/ui/panels/base_panel_browser_test.cc
index 8dc08096b91ca7c07445d1176c5e5b64fcccf353..6a0813c852f3f32501a7b5523501658111c9b448 100644
--- a/chrome/browser/ui/panels/base_panel_browser_test.cc
+++ b/chrome/browser/ui/panels/base_panel_browser_test.cc
@@ -182,10 +182,6 @@ void BasePanelBrowserTest::SetUpOnMainThread() {
   EXPECT_TRUE(ui_test_utils::BringBrowserWindowToFront(browser()));
 }
 
-// TODO(prasadt): If we start having even more of these WaitFor* pattern
-// methods, refactor. The only way to refactor would be to pass in a function
-// pointer, it may not be worth complicating the code till we have more of
-// these.

[Dmitry Titov, 2011/11/02 22:15:01]

I removed this because a) it is of "if in the future" sort, and future is always
not as expected b) in tests, it's better to go for simplicity rather then code
reuse, because 'automatic feature pick up' in tests may be exactly not a good
thing (changes what is tested) and should be done rather explicitly.
In other words, this seems to be a not specific comment better suited for design
discussion then a TODO in code.

 void BasePanelBrowserTest::WaitForPanelActiveState(
     Panel* panel, ActiveState expected_state) {
   DCHECK(expected_state == SHOW_AS_ACTIVE ||