Google Git
Sign in
chromium / external / github.com / WebKit / Speedometer / refs/heads/3.0-custom
commit6a536b3a11902491d9f882776999a7897bba8c2f[log] [tgz]
authorCamillo Bruni <[email protected]>Thu Apr 24 17:34:34 2025
committerCamillo Bruni <[email protected]>Thu Apr 24 17:34:59 2025
treee0ee8bc67947d9efd4015cb5575a86a4a890e3e0
parent4735260f42705d0f55a46e41ebf67d445ba690d6 [diff]
[speedometer][v3.0-custom] Add params.leakyIframes to main-custom

DevTools can't handle sources from detached iframes.
To simplify local development we add an an option that just hides
the iframes away but never detaches them from the DOM.

Drive-by-fix:
- Properly use markEnd

Change-Id: I037f7dfa7b3eb6c16f1aea0d12ea74703c95e562
5 files changed
tree: e0ee8bc67947d9efd4015cb5575a86a4a890e3e0
  1. .github/
  2. resources/
  3. tests/
  4. .eslintignore
  5. .eslintrc
  6. .gitignore
  7. .npmrc
  8. .prettierignore
  9. .prettierrc
  10. about.html
  11. babel.config.json
  12. Development.md
  13. Governance.md
  14. index.html
  15. instructions.html
  16. InteractiveRunner.html
  17. LICENSE
  18. package-lock.json
  19. package.json
  20. README.md
  21. Testing.md
README.md

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.