2 # The test directory can do whatever it wants in chrome, and may
9 # Tests under chrome/ shouldn't need to access the internals of content/ and
10 # as such are allowed only content/public. If you find yourself wanting to
11 # write such a test, or a test that depends primarily on content, think about
12 # whether the test belongs under content/, or should be split up into a test
13 # within content/ and a test within chrome/.
16 "+grit", # For generated headers