Demetrios PapadopoulosLGTM with nits, but also see CodeCoverage warnings about low coverage.
Shakti SahuMarking this unresolved to make sure it is not missed. Do you plan to address the code coverage warnings? Or did they go away somehow?
Thanks for flagging this. Filed b/477384509 to address this. We can have unit test that direclty instantiate the page handler.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Demetrios PapadopoulosLGTM with nits, but also see CodeCoverage warnings about low coverage.
Shakti SahuMarking this unresolved to make sure it is not missed. Do you plan to address the code coverage warnings? Or did they go away somehow?
Thanks for flagging this. Filed b/477384509 to address this. We can have unit test that direclty instantiate the page handler.
Thanks for filing. BTW, is there a reason to prefer the internal bug tracker for all things related to this feature? Note that Chromium is primarily an open source project and the open source tracker should be preferred unless there is a good reason.
See https://www.chromium.org/issue-tracking/googler-guidelines/#guidelines and specifically the part that says
**"Bugs should be open by default, unless there is specific information that should be restricted to Googlers. Chromium is an open-source project."**