[Lighthouse] Remove DOM check when adding view trace button

Lighthouse's `addButton` handles this for us–and besides,
the DOM has changed and this check is no longer valid.

Bug: 1262253
Change-Id: I63a1442a07fb139a6a7d760f76d57e546b36e0f7
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3237595
Reviewed-by: Connor Clark <cjamcl@chromium.org>
Commit-Queue: Connor Clark <cjamcl@chromium.org>
Auto-Submit: Paul Irish <paulirish@chromium.org>
This commit is contained in:
Paul Irish
2021-10-21 20:32:19 +00:00
committed by Devtools-frontend LUCI CQ
parent 1139798e6b
commit 6ee740ea29
@@ -51,11 +51,6 @@ export class LighthouseReportRenderer extends LighthouseReport.ReportRenderer {
if (!container) {
return;
}
const disclaimerEl = container.querySelector('.lh-metrics__disclaimer');
// If it was a PWA-only run, we'd have a trace but no perf category to add the button to
if (!disclaimerEl) {
return;
}
const defaultPassTrace = artifacts.traces.defaultPass;
const text = simulated ? i18nString(UIStrings.viewOriginalTrace) : i18nString(UIStrings.viewTrace);