Closed Bug 1791046 Opened 2 years ago Closed 2 years ago

Remove deprecated cookie lifetime policy API and deprecated setpermission-string API

Categories

(GeckoView :: General, task, P2)

Firefox 106
All
Android

Tracking

(firefox105 wontfix, firefox106 wontfix, firefox107 fixed)

RESOLVED FIXED
107 Branch
Tracking Status
firefox105 --- wontfix
firefox106 --- wontfix
firefox107 --- fixed

People

(Reporter: owlish, Assigned: owlish)

References

Details

(Whiteboard: [geckoview:m106])

Attachments

(1 file)

Remove the API marked with @DeprecationSchedule(id = "cookie-lifetime-policy", version = 106)

Whiteboard: [geckoview:m107]
Assignee: nobody → bugzeeeeee

We want to remove this API in 106.

Do Fenix or A-C still use this API?

Severity: -- → N/A
Priority: -- → P2
Whiteboard: [geckoview:m107] → [geckoview:m106]
Pushed by istorozhko@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2c2bc5fd317f
Remove deprecated cookie lifetime policy API r=geckoview-reviewers,calu
Flags: needinfo?(bugzeeeeee)
Summary: Remove deprecated cookie lifetime policy API → Remove deprecated cookie lifetime policy API and deprecated setpermission-string API
Attachment #9294987 - Attachment description: Bug 1791046 - Remove deprecated cookie lifetime policy API → Bug 1791046 - Remove deprecated cookie lifetime policy API and deprecated set permission API
Pushed by istorozhko@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/eb67fd2d8e06
Remove deprecated cookie lifetime policy API and deprecated set permission API r=geckoview-reviewers,calu

(In reply to Chris Peterson [:cpeterson] from comment #2)

We want to remove this API in 106.

Do Fenix or A-C still use this API?

I checked, they appear not to

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch

Irene, do we need to uplift this API removal to Beta 106?

Flags: needinfo?(bugzeeeeee)

No, I don't think so - the main problem with this was that these errors were failing the builds. Now that this is merged, the builds work again. As far as consumers are concerned - they don't use these anyways, so uplifting would not help any (unless there is a failing Beta 106 build that fails because of these deprecation errors).

Flags: needinfo?(bugzeeeeee)

Thanks. In that case, I'll set status-firefox106=wontfix.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: