Handle null TabSpecificContentSettings in PageInfo
TabSpecificContentSettings is bound to the page (aka main frame) and might be null at times this TabSpecificContentSettings clients should be able to tolerate null instances. Bug: 1096101 Change-Id: I6aa51f710a92cd883727525a2adf65b2588b5e98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2260617 Commit-Queue: Carlos Caballero <carlscab@google.com> Reviewed-by:Alexander Timin <altimin@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#781813}
Showing
Please register or sign in to comment