commit | c7953ceb3a985a50ed84be577c8a54a3a6551a13 | [log] [tgz] |
---|---|---|
author | Elad Alon <eladalon@chromium.org> | Tue May 13 07:46:15 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 13 07:46:15 2025 |
tree | d3a3d04714f8b92975e94685fc55090652dcb4b0 | |
parent | 2bf0ed4efe0a12bde681d5ab2328f40f9cf01f36 [diff] |
Improve webrtc_internals.html - move <details> templates Three templates which are currently populated by <details> are designed to appear at the top of the page. However, the HTML is structured misleadingly, putting them further down in the file than they end up appearing in the DOM. Until now, this has only been degrading readability and maintainability, and was therefore low-priority to fix. But a follow-up CL changes these templates into more straightforward <details> elements, which means that order would matter. We therefore move these objects into the more appropriate location on the page. This change is done separately from the next CL so as to aid readability. The current CL just moves the affected sections without modifying the code. Bug: 417262733 Change-Id: Ie321f915665fb63b39d200aba0c3622fe76d6d6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6533312 Reviewed-by: Philip Eliasson <philipel@chromium.org> Commit-Queue: Elad Alon <eladalon@chromium.org> Cr-Commit-Position: refs/heads/main@{#1459272}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.