You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
Introduce <perf-runner> (non-visual) and <perf-reporter> (visual). The runner should report results of the on-going performance test via attributes and/or events to the reporter.
I wonder why the current <perf-tester> puts the results using string concatenation instead of templates into the text content. Is this to have a plain web-component (without Polymer's template stamps), or to not falsify the timing results?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Introduce
<perf-runner>
(non-visual) and<perf-reporter>
(visual). The runner should report results of the on-going performance test via attributes and/or events to the reporter.perf-tester/demo/runner.html
Lines 27 to 36 in 05908d5
I wonder why the current
<perf-tester>
puts the results using string concatenation instead of templates into the text content. Is this to have a plain web-component (without Polymer's template stamps), or to not falsify the timing results?The text was updated successfully, but these errors were encountered: