| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// LINT.ThenChange(//content/browser/webid/delegation/email_verification_request.h:EvpRequestStatus)this belongs to EmailVerificationRequestResult, so there should probably be no newline before this but a newline after this
also should there be something similar for the list in Audits.pdl?
and do we really need the mojom version and the .h version? could we just use the mojom version directly in the C++ code?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
we may want to also add some more details to these issues (e.g. issuer domain) but that can be done later
| Commit-Queue | +1 |
we may want to also add some more details to these issues (e.g. issuer domain) but that can be done later
// LINT.ThenChange(//content/browser/webid/delegation/email_verification_request.h:EvpRequestStatus)this belongs to EmailVerificationRequestResult, so there should probably be no newline before this but a newline after this
also should there be something similar for the list in Audits.pdl?
and do we really need the mojom version and the .h version? could we just use the mojom version directly in the C++ code?
Regarding using mojom as the single source of the enum, as chatted offline, it might be suboptimal to keep the core enum (for metrics and other potential purposes) defined under devtools. We could introduce a new third_party/blink/public/mojom/webid/email_verification_request.mojom as the single source of truth but there's also a concern regarding importing high-level feature specific mojom into low-level ones. Please let me know which works for you. We could also ask the mojom owner for advice if needed.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Yi Guwe may want to also add some more details to these issues (e.g. issuer domain) but that can be done later
Is it the `kInvalidEmail` in https://chromium-review.git.corp.google.com/c/chromium/src/+/7849254/3/content/browser/webid/delegation/email_verification_request.cc#125?
Just generally I meant more information. For that kInvalidEmail we don't actually have an issuer domain. But e.g. when we have a network error from the issue endpoint, maybe we should show the URL we tried to contact. etc.
But again, we can do that later.
// LINT.ThenChange(//content/browser/webid/delegation/email_verification_request.h:EvpRequestStatus)Yi Guthis belongs to EmailVerificationRequestResult, so there should probably be no newline before this but a newline after this
also should there be something similar for the list in Audits.pdl?
and do we really need the mojom version and the .h version? could we just use the mojom version directly in the C++ code?
Regarding using mojom as the single source of the enum, as chatted offline, it might be suboptimal to keep the core enum (for metrics and other potential purposes) defined under devtools. We could introduce a new third_party/blink/public/mojom/webid/email_verification_request.mojom as the single source of truth but there's also a concern regarding importing high-level feature specific mojom into low-level ones. Please let me know which works for you. We could also ask the mojom owner for advice if needed.
I agree that using devtools as the source of truth is not ideal. I was just hoping that we could find a way to not have 3 copies of these values :/
but I trust your judgement on this, if you want to land as-is.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
PTAL. Thanks!
// LINT.ThenChange(//content/browser/webid/delegation/email_verification_request.h:EvpRequestStatus)Yi Guthis belongs to EmailVerificationRequestResult, so there should probably be no newline before this but a newline after this
also should there be something similar for the list in Audits.pdl?
and do we really need the mojom version and the .h version? could we just use the mojom version directly in the C++ code?
Christian BiesingerRegarding using mojom as the single source of the enum, as chatted offline, it might be suboptimal to keep the core enum (for metrics and other potential purposes) defined under devtools. We could introduce a new third_party/blink/public/mojom/webid/email_verification_request.mojom as the single source of truth but there's also a concern regarding importing high-level feature specific mojom into low-level ones. Please let me know which works for you. We could also ask the mojom owner for advice if needed.
I agree that using devtools as the source of truth is not ideal. I was just hoping that we could find a way to not have 3 copies of these values :/
but I trust your judgement on this, if you want to land as-is.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
using EvpRequestStatus = blink::mojom::EmailVerificationRequestResult;Have you considered keeping the original name? I tend to find it more difficult to follow code when it renames enums like this.
using EvpRequestStatus = blink::mojom::EmailVerificationRequestResult;I wouldn't use `using` in a header file like this
using EvpRequestStatus = blink::mojom::EmailVerificationRequestResult;same here
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
+Dave for everything but c/b/webid/. PTAL. Thanks!
using EvpRequestStatus = blink::mojom::EmailVerificationRequestResult;Have you considered keeping the original name? I tend to find it more difficult to follow code when it renames enums like this.
Done
using EvpRequestStatus = blink::mojom::EmailVerificationRequestResult;I wouldn't use `using` in a header file like this
Done
using EvpRequestStatus = blink::mojom::EmailVerificationRequestResult;Yi Gusame here
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
From googleclient/chrome/chromium_gwsq/ipc/config.gwsq:
IPC: ort...@chromium.org
📎 It looks like you’re making a possibly security-sensitive change! 📎 IPC security review isn’t a rubberstamp, so your friendly security reviewer will need a fair amount of context to review your CL effectively. Please review your CL description and code comments to make sure they provide context for someone unfamiliar with your project/area. Pay special attention to where data comes from and which processes it flows between (and their privilege levels). Feel free to point your security reviewer at design docs, bugs, or other links if you can’t reasonably make a self-contained CL description. (Also see https://cbea.ms/git-commit/).
IPC reviewer(s): ort...@chromium.org
Reviewer source(s):
ort...@chromium.org is from context(googleclient/chrome/chromium_gwsq/ipc/config.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
7 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: content/browser/webid/delegation/email_verification_request_unittest.cc
Insertions: 528, Deletions: 80.
The diff is too large to show. Please review the diff.
```
```
The name of the file: third_party/blink/public/mojom/webid/email_verification_request.mojom
Insertions: 3, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: tools/metrics/histograms/metadata/blink/enums.xml
Insertions: 3, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: third_party/blink/public/devtools_protocol/domains/Audits.pdl
Insertions: 3, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: content/browser/webid/delegation/email_verification_request.cc
Insertions: 166, Deletions: 39.
The diff is too large to show. Please review the diff.
```
```
The name of the file: content/browser/devtools/devtools_instrumentation.cc
Insertions: 8, Deletions: 0.
The diff is too large to show. Please review the diff.
```
```
The name of the file: content/browser/webid/delegation/email_verification_request.h
Insertions: 7, Deletions: 0.
The diff is too large to show. Please review the diff.
```
[EVP] Add DevTools issues for EVP failures
The frontend is implemented in crrev.com/c/7850416
NO_IFTTT=There was a missing enum change from ToT.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |