Gil Hanan

Yes of course, > when we access the native element directly we are giving up on Angular’s DOM abstraction and miss out on the opportunity to be able to execute...

There's no currently main benefit, maybe planing for you next course, Angular 2 Native: First Look :)

duplicating: https://github.com/johnpapa/angular-styleguide/pull/780/files

@Thatkookooguy The difference is when using the syntactic sugar, you have to use the variable declared in the scope, which can be confuse and hard to maintenance, because it's managed...

I think ability to load configuration options as module would solved that

I would happy for review, meantime i will work on docs

@fanczerni @aganglada @oh-roman When there is more than one slide to show, managing the active slides for `hidden` others is too complicated when there are responsive settings for slides to...

Same scenario for me.

that's because the perfomance graph value is calculated as the [median](https://github.com/GoogleChrome/lighthouse-ci/blob/cde4a48118a9be48e914c656591301ebed6972db/packages/server/src/api/statistic-definitions.js#L129) value of the whole performance category runs: ``` javascript category_performance_median: categoryScoreMedian('performance') ``` while the report is the most [representitve](https://github.com/GoogleChrome/lighthouse-ci/blob/4f507323e9ea3b4b4757d74829c2a858d08bc12e/packages/utils/src/representative-runs.js#L29)...

I'm also expereince this issue. If someone want to repro it easily: `npx @lhci/cli autorun --collect.url=https://gh-lhci-azure-demo-app---staging.jollyrock-437e64c9.northeurope.azurecontainerapps.io --assert.preset=lighthouse:no-pwa` ``` × total-byte-weight failure for minScore assertion Avoids enormous network payloads https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/ expected:...