chromium/src
0
Fork 0
Code Activity

Remove mentions of Lacros from docs/*, part 2

Browse Source 
Change-Id: Ie2522305dcd16aec08fc13e862b67963d11c16a3
Bug: b:365688694
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5849449
Reviewed-by: Yuta Hijikata <ythjkt@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1353195}
This commit is contained in:
Georg Neis
2024-09-10 08:21:27 +00:00
committed by Chromium LUCI CQ
parent 05bb049e0d
commit c5cca748d6
3 changed files with 3 additions and 10 deletions
docs
media
capture
README.md
speed
binary_size
metrics.md
webui_explainer.md

1
docs/media/capture/README.md

@ -39,7 +39,6 @@ below.
* Code
* Windows/Linux: `//third_party/webrtc/modules/desktop_capture`
* Mac: `//content/browser/media/capture/desktop_capture_device_mac.cc`
* LaCrOS: `//content/browser/media/capture/desktop/desktop_capturer_lacros.cc`
* Issues
* `Internals>Media>ScreenCapture`
* Docs

5
docs/speed/binary_size/metrics.md

@ -94,8 +94,3 @@ For Googlers, more information available at [go/chrome-apk-size](https://goto.go
* [Telemetry Graph](https://chromeperf.appspot.com/report?sid=33f59871f4e9fa3d155be3c13a068d35e6e621bcc98d9b7b103e0c8485e21097)
* Uncompressed size of classes.dex, locale .pak files, etc
* Reported only for things that are compressed within the .apk
## Metrics for LaCrOS
* Sizes are collected by
[//build/lacros/lacros_resource_sizes.py](https://cs.chromium.org/chromium/src/build/lacros/lacros_resource_sizes.py).

7
docs/webui_explainer.md

@ -1270,8 +1270,8 @@ TypeScript for a WebUI-based chrome:// page does one of the following:
* Calls `console.error()`.
Such errors will appear alongside other crashes in the
`product_name=Chrome_ChromeOS`, `product_name=Chrome_Lacros`, or
`product_name=Chrome_Linux` lists on [go/crash](http://go/crash).
`product_name=Chrome_ChromeOS` or `product_name=Chrome_Linux` lists on
[go/crash](http://go/crash).
The signature of the error is the error message followed by the URL on which the
error appeared. For example, if chrome://settings/lazy_load.js throws a
@ -1316,8 +1316,7 @@ error, JavaScript errors are currently all classified as "WARNING" level when
computing stability metrics.
### Known issues
1. Error reporting is currently enabled only on ChromeOS (ash and Lacros) and
Linux.
1. Error reporting is currently enabled only on ChromeOS and Linux.
2. Errors are only reported for chrome:// URLs.
3. Unhandled promise rejections do not have a good stack.
4. The line numbers and column numbers in the stacks are for the minified