diff --git a/src/Umbraco.Web.UI.Client/src/backoffice/dashboards/performance-profiling/dashboard-performance-profiling.element.ts b/src/Umbraco.Web.UI.Client/src/backoffice/dashboards/performance-profiling/dashboard-performance-profiling.element.ts index d04cbfb08c..78e8195064 100644 --- a/src/Umbraco.Web.UI.Client/src/backoffice/dashboards/performance-profiling/dashboard-performance-profiling.element.ts +++ b/src/Umbraco.Web.UI.Client/src/backoffice/dashboards/performance-profiling/dashboard-performance-profiling.element.ts @@ -56,61 +56,62 @@ export class UmbDashboardPerformanceProfilingElement extends UmbContextConsumerM connectedCallback(): void { super.connectedCallback(); this._getProfilingStatus(); - if (localStorage.getItem('profilingPerformance') === 'true') this._profilingPerfomance = true; - else this._profilingPerfomance = false; + this._profilingPerfomance = localStorage.getItem('profilingPerformance') === 'true'; } private _changeProfilingPerformance() { this._profilingPerfomance = !this._profilingPerfomance; - this._profilingPerfomance - ? localStorage.setItem('profilingPerformance', 'true') - : localStorage.setItem('profilingPerformance', 'false'); + localStorage.setItem('profilingPerformance', this._profilingPerfomance.toString()); + } + + private renderProfilingStatus() { + return this._profilingStatus + ? html` +
+ Umbraco currently runs in debug mode. This means you can use the built-in performance profiler to assess the + performance when rendering pages. +
++ If you want to activate the profiler for a specific page rendering, simply add + umbDebug=true to the querystring when requesting the page. +
+ ++ If you want the profiler to be activated by default for all page renderings, you can use the toggle below. + It will set a cookie in your browser, which then activates the profiler automatically. In other words, the + profiler will only be active by default in your browser - not everyone else's. +
+ ++ You should never let a production site run in debug mode. Debug mode is turned off by setting + Umbraco:CMS:Hosting:Debug to false in appsettings.json, appsettings.{Environment}.json or via an environment + variable. +
+ ` + : html` ++ Umbraco currently does not run in debug mode, so you can't use the built-in profiler. This is how it should + be for a production site. +
++ Debug mode is turned on by setting debug="true" on the <compilation /> element in + web.config. +
+ `; } render() { return html`- Umbraco currently runs in debug mode. This means you can use the built-in performance profiler to assess - the performance when rendering pages. -
-- If you want to activate the profiler for a specific page rendering, simply add - umbDebug=true to the querystring when requesting the page. -
- -- If you want the profiler to be activated by default for all page renderings, you can use the toggle - below. It will set a cookie in your browser, which then activates the profiler automatically. In other - words, the profiler will only be active by default in your browser - not everyone else's. -
- -- You should never let a production site run in debug mode. Debug mode is turned off by setting - Umbraco:CMS:Hosting:Debug to false in appsettings.json, appsettings.{Environment}.json or via an - environment variable. -
- ` - : html` -- Umbraco currently does not run in debug mode, so you can't use the built-in profiler. This is how it - should be for a production site. -
-- Debug mode is turned on by setting debug="true" on the <compilation /> element in - web.config. -
- `} + ${typeof this._profilingStatus === 'undefined' ? html`