Closed Bug 1202734 Opened 9 years ago Closed 9 years ago

Add webRequest requestId property

Categories

(WebExtensions :: Untriaged, defect, P2)

Product:
WebExtensions
Component:
Untriaged
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1163862
Iteration:
47.2 - Feb 22

People

(Reporter: billm, Assigned: ma1)

References

(Blocks 1 open bug)

Details

(Whiteboard: [webRequest]triaged)

To do this, we'll need everything to run in the parent process. That means that the content policy stuff will have to be moved to an http-on-modify handler or something.
Whiteboard: [webRequest]
Blocks: webext-port-noscript
Blocks: webext
Flags: blocking-webextensions+
Blocks: webRequest-full
Assignee: nobody → g.maone
Iteration: --- → 45.3 - Dec 14
Iteration: 45.3 - Dec 14 → 46.1 - Dec 28
Iteration: 46.1 - Dec 28 → 46.2 - Jan 11
Iteration: 46.2 - Jan 11 → 46.3 - Jan 25
Iteration: 46.3 - Jan 25 → 47.1 - Feb 8
Depends on: 1163862
Whiteboard: [webRequest] → [webRequest]triaged
Priority: -- → P2
Iteration: 47.1 - Feb 8 → 47.2 - Feb 22
making major as needed for ghostery - 15M users
Severity: normal → major
make that 1.5M users - still major impact
No longer blocks: e10s-noscript
This is being fixed by the patch I've just attached to bug 1163862. Should I resolve this one as a dupe?
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.