Open Bug 1425570 Opened 7 years ago Updated 2 years ago

Add a combination of deleteRange and deleteUrl

Categories

(WebExtensions :: General, enhancement, P5)

57 Branch
enhancement

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: core, Unassigned)

Details

(Whiteboard: [design-decision-approved][history])

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171206182557 Steps to reproduce: I wanted to remove all history entries of a certain url within a given time range (in this case all history logged in this session). Actual results: The API isn't capable of doing this right now. deleteUrl() allows to remove by url deleteRange() allows to remove by a time range Expected results: There needs to be another (possibly more generic) remove() method which accepts both url and startTime/endTime.
Alternatively, a way to remove VisitItems by Id would be an option.
Severity: normal → enhancement
Priority: -- → P5
Whiteboard: [design-decision-needed]
Summary: History: Add a combination of deleteRange and deleteUrl → Add a combination of deleteRange and deleteUrl
Whiteboard: [design-decision-needed] → [design-decision-needed][history]
Hi Lusito, this has been added to the agenda for the January 30, 2018 WebExtensions APIs triage meeting. Would you be able to join us? Here’s a quick overview of what to expect at the triage: * We normally spend 5 minutes per bug * The more information in the bug, the better * The goal of the triage is to give a general thumbs up or thumbs down on a proposal; we won't be going deep into implementation details Relevant Links: * Wiki for the meeting: https://wiki.mozilla.org/WebExtensions/Triage#Next_Meeting * Meeting agenda: https://docs.google.com/document/d/1x80jYXicAotNjlitY5RZDcSRpRM3lmaSHp_q4co4OEg/edit# * Vision doc for WebExtensions: https://wiki.mozilla.org/WebExtensions/Vision
Hi Caitlin, this should be possible.
Flags: needinfo?(mconca)
Whiteboard: [design-decision-needed][history] → [design-decision-approved][history]
This API request was approved as part of the 30-Jan-2018 design decision meeting. When this is implemented, it will be important to maintain Chrome compatibility with the current API. Possibilities discussed during the meeting included adding a completely new API or possibly extending the current API with different options.
Flags: needinfo?(mconca)
Product: Toolkit → WebExtensions
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.