Google GitGoogle Git
Sign in
chromium/external/github.com/WebKit/Speedometer/2414364b185d89310c4e098158f4df9932a2e235
commit
2414364b185d89310c4e098158f4df9932a2e235
[log]
author
Julien Wajsberg <felash@gmail.com>
Wed Nov 29 18:17:06 2023
committer
GitHub <noreply@github.com>
Wed Nov 29 18:17:06 2023
tree
56d60ec2ca20e3c502164dcfb596047cc7f4e663
parent
208e1abee2916fe4404c4ac561d80ee92dfee059 [diff]
Keep the parameter 'tags' as an array in the body of the function (#337)

Previously, we were transforming it into a set. This was giving problems
in a later condition, so that no message/debugInfo were defined, and the
user would get an alert with the message "undefined".

Now the set stays local to the code block where it's used, so that the
parameter variable "tags" is an array for the whole function, for more
consistency with the "names" variable.
1 file changed
tree: 56d60ec2ca20e3c502164dcfb596047cc7f4e663
  1. .github/
  2. resources/
  3. tests/
  4. .eslintignore
  5. .eslintrc
  6. .gitignore
  7. .npmrc
  8. .prettierignore
  9. .prettierrc
  10. babel.config.json
  11. Development.md
  12. Governance.md
  13. index.html
  14. InteractiveRunner.html
  15. LICENSE
  16. package-lock.json
  17. package.json
  18. README.md
  19. Testing.md
README.md
:warning: Speedometer 3 is in active development and is unstable. You can follow along with development in this repository, but see Speedometer 2.1 for the latest stable version.

What is Speedometer?

Speedometer is a benchmark for web browsers that measures Web application responsiveness by timing simulated user interactions on various workloads. Our primary goal is to make it reflect the real-world Web as much as possible. When a browser improves its score on the benchmark, actual users should benefit. In order to achieve this, it should:

  • Test end-to-end user journeys instead of testing specific features in a tight loop. Each test should exercise the full set of what’s needed from the engine in order for a user to accomplish a task.
  • Evolve over time, adapting to the present Web on a regular basis. This should be informed by current usage data, and by consensus about features which are important for engines to optimize to provide a consistent experience for users and site authors.
  • Be accessible to the public and useful to browser engineers. It should run in every modern browser by visiting a normal web page. It should run relatively quickly, while providing enough test coverage to be reflective of the real-world Web.