Fixed invalid DOM nesting warning
Brian Vaughn committed
May 7, 2019 at 15:25 UTC
a54581c2ddca06d6e0eabf87c90e276c6e7a0987
2 files changed
+9
-8
src/devtools/views/Profiler/NoCommitData.css
+1
@@ -9,6 +9,7 @@
9
10
.Header {
11
font-size: var(--font-size-sans-large);
12
+ margin-bottom: 0.5rem;
13
}
14
15
.FilterMessage {
src/devtools/views/Profiler/NoCommitData.js
+8
-8
@@ -12,25 +12,25 @@ export default function NoCommitData(_: {||}) {
12
if (rootHasProfilingData) {
13
return (
14
<div className={styles.NoCommitData}>
15
- <p className={styles.Header}>
15
+ <div className={styles.Header}>
16
There is no data matching the current filter criteria.
17
- </p>
18
- <p className={styles.FilterMessage}>
17
+ </div>
18
+ <div className={styles.FilterMessage}>
19
Try adjusting the commit filter <ToggleCommitFilterModalButton />
20
- </p>
20
+ </div>
21
</div>
22
);
23
} else {
24
return (
25
<div className={styles.NoCommitData}>
26
- <p className={styles.Header}>
26
+ <div className={styles.Header}>
27
There is no timing data to display for the currently selected commit.
28
- </p>
29
- <p>
28
+ </div>
29
+ <div>
30
This can indicate that a render occurred too quickly for the timing
31
API to measure. Try selecting another commit in the upper, right-hand
32
corner.
33
- </p>
33
+ </div>
34
</div>
35
);
36
}