This CL adds documentation on how to build the content shell for Apple
tvOS and how to launch it on the simulator. Most of the environment
setup steps are shared with iOS, so the instructions have been added to
the existing iOS build guide.
Co-authored with Raphael Kubo da Costa <kubo@igalia.com>
Bug: 391914246
Change-Id: Ica509667908f8ba707e91e406d1dc6ef3f1fad55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6572972
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1464370}
Change grit to remove kFooResourcesSize and associated includes. They
are not longer needed, as all uses have been converted. Update WebUI
documents to stop referring to them as well.
Bug: 347651465
Change-Id: Ica6c3911c0484c49deccd54e49c89eea65c9175c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6557890
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1464310}
This change updates the lldbinit docs with a note that the path to the
lldb/ directory should be absolute. I ran into issues after using "~/"
and hope this saves future readers the same trouble.
This CL also does a bit of formatting:
* limit line widths to 80 characters where possible
* make some phrasing more concise
Change-Id: I7fdfdcfc1982481a3b3cb1968b526b13922511da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6559130
Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Commit-Queue: Jesse McKenna <jessemckenna@google.com>
Cr-Commit-Position: refs/heads/main@{#1463005}
* Remove references to how things worked before Xcode 9, which was
released in 2017.
* Remove references to the Chromium IRC channel, which was shut down in
2021. Direct people to Slack and the mailing lists instead.
Change-Id: Iaf019ef8d38950f44690aced900c8b4aea7ffc63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6565543
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Auto-Submit: Raphael Kubo da Costa <kubo@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1462668}
Updates the documentation of TabHelpers to specify using TabFeatures
instead. At this point in time, TabFeatures can be used on Desktop and
Android.
When possible prefer TabFeatures over TabHelpers.
Change-Id: Icd32a2eddbe7c1492d1655d30d533d3a9cff9592
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6565952
Commit-Queue: Darryl James <dljames@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1462399}
This suggested change is automatically generated based on group
memberships and affiliations.
Please approve this change and vote the highest CR. This will keep the
OWNERS file tidy. We ask that you do not ignore this change and either
approve it if the OWNER is no longer active or deny it if the OWNER is
continuing to review CLs (including under a different affiliation).
This CL can always be reverted if the understanding changes.
If this change is in error, vote the lowest CR value (i.e. reject the
CL) and the bot will abandon it.
See the owner's recent review activity for context:
https://chromium-review.googlesource.com/q/bkersting@google.com
To report an issue, file a bug in the Infra>Codereview component.
Change-Id: I930935c8987fc7c10f1e6d1cf734776d24a49bf9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6559722
Commit-Queue: Owners Cleanup <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com>
Auto-Submit: Owners Cleanup <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com>
Reviewed-by: Ethan Cheng <yycheng@google.com>
Cr-Commit-Position: refs/heads/main@{#1462274}
This suggested change is automatically generated based on group
memberships and affiliations.
Please approve this change and vote the highest CR. This will keep the
OWNERS file tidy. We ask that you do not ignore this change and either
approve it if the OWNER is no longer active or deny it if the OWNER is
continuing to review CLs (including under a different affiliation).
This CL can always be reverted if the understanding changes.
If this change is in error, vote the lowest CR value (i.e. reject the
CL) and the bot will abandon it.
See the owner's recent review activity for context:
https://chromium-review.googlesource.com/q/adetaylor@chromium.org
To report an issue, file a bug in the Infra>Codereview component.
Change-Id: Idc44d05afa0889002c2b328f690b4b5e3cd4965e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6561316
Auto-Submit: Owners Cleanup <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1461942}
We believe this to be unused (outside of tests), and the existence of
the functionality has caused confusion when talking about non-DMG
updates on macOS.
Generally, we're not aware of a good reason to ship CRX(ZIP(stuff))
instead of CRX(stuff).
Fixed: 417755591
Change-Id: I69714265eb8261145c2682faa04a19ec01b85206
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6545870
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1460932}
Specifically, this change adds a new //SECURITY_OWNERS file, then marks
all SECURITY_OWNERS files elsewhere in the tree as owned by that
SECURITY_OWNERS file. This will help enforce the SECURITY_OWNERS
membership policy documented in //docs/security/security-owners.md.
Note that it is still possible for OWNERS files in subdirectories to
override this root rule: a more-specific OWNERS file will always
override a less-specific one. We will monitor for that situation using
watchlists, in the absence of a better technical measure to apply.
Bug: 417401758
Change-Id: I7a7bca2cbc7a36ccab04310ff7b0d6cc09fde737
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6542689
Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1460364}
Updated the relative link from security/rule-of-2.md to
../security/rule-of-2.md to correctly reference the rule-of-2
documentation located in the parent directory.This change prevents
broken links and improves navigation consistency across the docs.
Bug: None
Change-Id: I48a0838348c3e427b4349601ae5ea074404b2ec4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6522308
Reviewed-by: Euisang Lim <eui-sang.lim@samsung.com>
Commit-Queue: Euisang Lim <eui-sang.lim@samsung.com>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1459835}
This structure allows us to clearly separate third and first
party code in third party directories. This structure is
applicable for dependencies that are DEPS'd and those that
are vendored (checked-in). This will greatly help our
observability by moving metadata files and third party code
to a predictable location in a chromium checkout and allowing
us to produce clean diffs with upstream.
Bug: 40092732
Change-Id: I244022b1579de4b837512548b2f29ab23bd49c0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6449781
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Rachael Newitt <renewitt@google.com>
Cr-Commit-Position: refs/heads/main@{#1457915}
- Updated the SQL to make it work. Especially, fixed typos.
- Removed the SQLs that does not have meaningful data any more.
Especially, I do not think the latest httparchive.pages.*
have $._blinkFeatureFirstUsed.Features.*.
Also, there is no table like httparchive.runs.*
Change-Id: I6852260493e1fab1a5319e91c6818d1d49f1f74d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6051114
Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Shunya Shishido <sisidovski@chromium.org>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1457433}
It looks like Android Studio went through a UI refresh so now the
emulator flow is very different. I've updated this based on the new UI
and also included screenshots.
Test: Upload to gerrit > open file > click "preview"
Change-Id: I8750cada26bd5b5c94dbe264508edcf7bcd1e096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6519478
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1457377}
Rational:
1. Wpt expectation updator seems to have problem to handle another
test expectation file. Currently Wpt importer is adding webview
expectations to TestExpectations, instead of MobileTestExpectations.
2. Developers are used to add test expectations to TestExpectations,
e.g. crrev.com/c/6089100.
Also removed some stale test expectations.
Bug: 40279492
Change-Id: I25a7d078f3ea73d8be5a71d95d8fa82b25979fa9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6520154
Reviewed-by: Jonathan Lee <jonathanjlee@google.com>
Commit-Queue: Weizhong Xia <weizhong@google.com>
Cr-Commit-Position: refs/heads/main@{#1457279}
This CL introduces a `Force Install` feature that does the following:
* Force-installs the metainstaller that is run with the
`--force-install` switch and makes it the active `updater`.
* Installs the application(s) that are implicitly specified in the
tagged metainstaller, or explicitly specified using the `--install` or
`--handoff` parameters.
Bug: 408017292
Change-Id: Idd20afb7fe9980fb6cce977b953c82a121cb4f8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6508105
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Auto-Submit: S Ganesh <ganesh@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1456197}
This CL updates the outdated information about LLVM/Clang.
- updates the directory structure. tools/ directory doesn't exist
anymore.
- updates Diagnostic::Warning to DiagnosticsEngine::Warning.
- updates instance.getCustomDiagID() to instance.getDiagnostics().getCustomDiagID.
- wraps the lines to 80 characters.
Change-Id: If543d88afc709fa52da657fc0f055411fa5befdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6495335
Commit-Queue: Asami Doi <asamidoi@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1456185}
When the "current shepherds" script is redeployed, it ends up running at
a new URL. By using a go link, maintainers of the "current shepherds"
script can republish the script and update the go link without needing
to remember to update all references to the script.
Change-Id: Id6a5b2d763da434eb87c59153211870bf3149e75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6505688
Auto-Submit: Javier Castro <jacastro@chromium.org>
Reviewed-by: Amy Ressler <amyressler@chromium.org>
Commit-Queue: Amy Ressler <amyressler@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1455090}
This CL adds 2 new documentation files about web platform security:
* stop-leaks-policy.md: a new policy about XS-Leaks, explaining what are the main issues with XS-Leaks, and what are the things to look for when creating or implementing a new Web API or feature
* web-platform-security-questionnaire.md: a very basic questionnaire to help web platform teams identify potential security impacts in their web API design.
Change-Id: Ifbf4bb35b5fe525bdec4d32c168ddbee4feceace
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6495410
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Commit-Queue: Camille Lamy <clamy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1453937}
