New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 758496 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: 2017-09-08
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Since parameter of chrome.browsingData.remove cannot be set to 1 second before

Reported by quen...@econsulting.fr, Aug 24 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Create a close tab event listener
2. Create in this event listener a variable Date ( new Date().getTime() )
3. Remove 1000 millisecond to the previous variable
4 Set your chrome.browsingData.remove function with the previous variable as since parameter

What is the expected behavior?
Only the last entry of closed tab should be removed

What went wrong?
All entries of closed tab are removed

Did this work before? N/A 

Chrome version: 60.0.3112.101  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 26.0 r0
explanation.js
704 bytes View Download

Comment 1 by hdodda@chromium.org, Aug 25 2017

Cc: hdodda@chromium.org
Labels: Needs-Triage-M60 Needs-Feedback
Thanks for the report.. 

@quentin-- Could you please provide us the sample test file /url/jsfiddle demonstrating the issue for better traiging purpose.

Thanks!

Comment 2 by dtapu...@chromium.org, Aug 31 2017

NextAction: 2017-09-08

Comment 3 by rbyers@chromium.org, Sep 5 2017

Components: -Blink Platform>Extensions>API
This is about the chrome.browsingData extensions API - to extensions component.

Comment 4 by quen...@econsulting.fr, Sep 6 2017 

@hdodda : 
What do you mean by /url/jsfiddle ?

@rbyers : 
Yes this is about chrome.browsingData extensions API , precisely the remove function
Project Member

Comment 5 by sheriffbot@chromium.org, Sep 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by monor...@bugs.chromium.org, Sep 8 2017 

The NextAction date has arrived: 2017-09-08

Comment 7 by krajshree@chromium.org, Oct 17 2017

Status: WontFix (was: Unconfirmed)
There is no response from the reporter for more than one month.
Hence, closing the issue as wontFix.
Please feel free to raise a new issue if the issue is reproduced with latest chrome builds.

Thanks...!!
►

Sign in to add a comment