| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// The manifest of this test page does not contain an `id`, so we must set it
// on the element. It's the same as the install_url because the start_url is
// set to manifest_test_page.html.Suggestion - Consider using this test page instead where the install_url is different from the manifest_id: https://source.chromium.org/chromium/chromium/src/+/main:chrome/test/data/web_apps/install_url/?q=install_url%20test%2Fdata&ss=chromium
In a previous comment from Dan, he pointed out install url should be different than the start_url and manifest_id to prevent potential bugs and from the logic potentially mistaking one for the other, so it's possible he might suggest that again: https://chromium-review.googlesource.com/c/chromium/src/+/7006552/comment/5e35d593_2c76fd45/
Here's my CL where I updated our test sites to his suggestion: https://chromium-review.googlesource.com/c/chromium/src/+/7233302/3/chrome/browser/web_applications/commands/web_install_from_url_command_browsertest.cc
We could also consider updating the start_urls on the new test pages created in this CL so they're different from the install_url and manifest_id too.
<link rel="manifest" href="manifest_for_install_element.json">nit: For all the new test pages created, here's another potential location for them to consider: `chrome/test/data/web_apps/`
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |