dfried@ can you please take a look? I am splitting the CL you looked at into 5 sub CLs. The entire feature will likely be implemented over 12ish CLs
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
base::RecordAction(UserMetricsAction("ReportUnsafeSite_AppMenu"));nit: this naming convention doesn't seem to match any other app menu actions
if (feedback::ReportUnsafeSiteDialog::IsEnabled(*browser->profile())) {Should we wrap this in a GOOGLE_CHROME_BRANDING check as well?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
dfried@ can you please take another look?
base::RecordAction(UserMetricsAction("ReportUnsafeSite_AppMenu"));nit: this naming convention doesn't seem to match any other app menu actions
Removed _AppMenu suffix
if (feedback::ReportUnsafeSiteDialog::IsEnabled(*browser->profile())) {Should we wrap this in a GOOGLE_CHROME_BRANDING check as well?
Put IDC_FEEDBACK inside the GOOGLE_CHROME_BRANDING check as well. Let's see if the tests pass. The help menu isn't created at all for non-branded builds.
| 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. |
| 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. |