New issue
Advanced search Search tips

Issue 870725 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

anticipatedRemoval shows up as 0 instead of null in deprecation reports

Project Member Reported by paulmeyer@chromium.org, Aug 3

Issue description

Chrome Version: 70.0.3509.0
OS: All

What steps will reproduce the problem?
(1) Run Chrome with the flag "--enable-features=Reporting,NetworkErrorLogging"
(2) Use "window.webkitURL" in DevTools.
(3) Open chrome://net-internals/ in another tab and click "Reporting" on the left.
(4) Look at the full details of the queued deprecation report that was just generated.

What is the expected result?
This deprecated feature currently has no anticipated removal date, so the |anticipatedRemoval| field should be either null or absent.


What happens instead?
|anticipatedRemoval| is set to 0.


 

Sign in to add a comment