Bug 1380809 (webext-incognito)

[META] manifest incognito feature support

REOPENED
Unassigned

Status

enhancement
P3
normal
REOPENED
2 years ago
17 days ago

People

(Reporter: jgruen, Unassigned)

Tracking

(Depends on 12 bugs, Blocks 2 bugs, {meta})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
tracking bug for full support of incognito rules in WebExtensions. Note that Firefox Screenshots would make use of this work.
(Reporter)

Updated

2 years ago
Depends on: 1380812
(Reporter)

Updated

2 years ago
Summary: Support Incognito Key In WebExtnsions → Fully Support Incognito Key In WebExtnsions
(Reporter)

Updated

2 years ago
Summary: Fully Support Incognito Key In WebExtnsions → Fully Support Incognito Key In WebExtensions

Updated

2 years ago
Keywords: meta

Updated

2 years ago
Severity: normal → enhancement
Priority: -- → P3

Updated

2 years ago
Duplicate of this bug: 1377960
Duplicate of this bug: 1424353

Updated

a year ago
Duplicate of this bug: 1425177
Comment hidden (abuse-reviewed, advocacy)

Updated

a year ago
Duplicate of this bug: 1425377
Duplicate of this bug: 1432120
Comment hidden (abuse-reviewed)
(In reply to arnymars from comment #7)
> Only reporting new and new duplicates of this bug coming from countless
> users, but no progress whatsoever on fixing the issue. Despite Chrome has
> all web exts fully blocked in Private Windows. May be there is a need to
> remind FF devs how it affects their browser popularity and potential of
> loosing their job due to sharply dropping demand for the Firefox browser.
> 
> https://upload.wikimedia.org/wikipedia/commons/c/c5/StatCounter-browser-ww-
> monthly-200901-201707.png

Arynmars, I can understand your concern and your passion for this issue but commenting that developers should lose their jobs in this forum is inappropriate. Please read the Bugzilla Etiquette before you leave another comment: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
Blocks: 1457001
Blocks: 1460738

Updated

10 months ago
Product: Toolkit → WebExtensions
comment 0 here sounds like this was a meta bug, but we have meta bug 1460738, so closing this one.
No longer blocks: 1457001, 1460738
Status: NEW → RESOLVED
Last Resolved: 10 months ago
No longer depends on: 1345474, 1380812
Resolution: --- → DUPLICATE
Duplicate of bug: 1460738
Sorry for the spam.  Changed my mind as we have two buckets of bugs.  The first related to the incognito feature itself, and the other being bugs in various tests/apis related to private browsing mode.  We'll use this bug as the meta for the feature.  The parent meta bug 1460738 will list all bugs related to "improving incognito support"
Blocks: 1460738
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Summary: Fully Support Incognito Key In WebExtensions → [META] manifest incognito feature support
Comment hidden (advocacy)

Comment 12

7 months ago
Again what is the status on this?
As this is tracking bug, the status on this is reflected in the change of dependent bugs.
Flags: needinfo?(ddurst)
Depends on: 1506653
Depends on: 1511636
Depends on: 1513220
Depends on: 1513344
Depends on: 1513345
Depends on: 1513347
Depends on: 1513544

Updated

4 months ago
Depends on: 1515694

Updated

4 months ago
Depends on: 1515701
Depends on: 1516465
Depends on: 1516548
Depends on: 1516670
Depends on: 1516680
Depends on: 1516704
Depends on: 1516706
Depends on: 1516707
Depends on: 1516708
Depends on: 1516709
Depends on: 1516710
Depends on: 1516711
Depends on: 1359769
Depends on: 1452514
Depends on: 1309610
No longer depends on: 1380812

Updated

4 months ago
Depends on: 1518486
Depends on: 1518579
Depends on: 1521138
Depends on: 1521139
No longer depends on: 1359769
Depends on: 1521573
Depends on: 1521596
Depends on: 1521627
Depends on: 1523605
Depends on: 1523632
Depends on: 1524324
Depends on: 1512353
Depends on: 1525125
Depends on: 1523914
Depends on: 1525428
Depends on: 1525447
Depends on: 1525712
Depends on: 1525718

Updated

3 months ago
Depends on: 1525846
Depends on: 1526297
Depends on: 1526299
No longer depends on: 1452514
Depends on: 1527127

Updated

2 months ago
Depends on: 1529099
Depends on: 1529394
Depends on: 1529582

Updated

2 months ago
No longer depends on: 1380812
Depends on: 1531974
Depends on: 1531976
Depends on: 1532110
Depends on: 1532165
Depends on: 1532774
Depends on: 1532800
Depends on: 1533519

Updated

2 months ago
Depends on: 1533172
Depends on: 1534131
Depends on: 1534682
Depends on: 1534714

Comment 14

a month ago

I'm testing the incognito experience in Beta 67 with my add-ons and I've noticed one issue - Options page of each add-on will load broken (because of the javascript restrictions in API) - I would suggest to remove the "Options" button for add-ons that are not allowed in Private Brosing mode. I don't think there are add-ons that uses pure html Options page :)

Also, I've noticed that add-ons installed from Private Browsing mode are not implicitly allowed in Private mode, maybe that's expected?

(In reply to juraj.masiar from comment #14)

I'm testing the incognito experience in Beta 67 with my add-ons and I've noticed one issue - Options page of each add-on will load broken (because of the javascript restrictions in API) - I would suggest to remove the "Options" button for add-ons that are not allowed in Private Brosing mode. I don't think there are add-ons that uses pure html Options page :)

Can you add a new bug with steps to reproduce? cc me on it.

Also, I've noticed that add-ons installed from Private Browsing mode are not implicitly allowed in Private mode, maybe that's expected?

That is expected.

Best to not use our tracking bug for conversation. If there's an issue just add a bug, we'll triage it.

Thanks!

Depends on: 1537542
See Also: → 1538084
Alias: webext-incognito
Depends on: 1538583
Depends on: 1538546

Updated

a month ago
Depends on: 1533150

Updated

27 days ago
Depends on: 1540112

Updated

25 days ago
Depends on: 1540565

Updated

23 days ago
Depends on: 1540959

Updated

21 days ago
Depends on: 1541851
Depends on: 1542842
You need to log in before you can comment on or make changes to this bug.