Closed Bug 763628 Opened 12 years ago Closed 6 years ago

Include Android OS version and device information in the blocklist URL

Categories

(Toolkit :: Add-ons Manager, defect)

All
Android
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: laura, Unassigned)

Details

Why?
1.  We'd like to have ADU data per device/OS version
2.  We might conceivably want to block add-ons on a per device basis.
(In reply to Laura Thomson :laura from comment #0)
> Why?
> 1.  We'd like to have ADU data per device/OS version

What's happened with the metrics data ping that was meant to be replacing the blocklist for ADU info?

> 2.  We might conceivably want to block add-ons on a per device basis.

We shouldn't use the URL for this, the blocklist should be the same regardless of the device/os/etc.
(In reply to Dave Townsend (:Mossop) from comment #1)
> (In reply to Laura Thomson :laura from comment #0)
> > Why?
> > 1.  We'd like to have ADU data per device/OS version
> 
> What's happened with the metrics data ping that was meant to be replacing
> the blocklist for ADU info?

It may be that's the right way to do this: I don't mind how.  Daniel Einspanjer suggested I file this bug here.

> 
> > 2.  We might conceivably want to block add-ons on a per device basis.
> 
> We shouldn't use the URL for this, the blocklist should be the same
> regardless of the device/os/etc.

I'll let somebody from mobile comment on that.
(In reply to Laura Thomson :laura from comment #2)
> (In reply to Dave Townsend (:Mossop) from comment #1)
> > (In reply to Laura Thomson :laura from comment #0)
> > > 2.  We might conceivably want to block add-ons on a per device basis.
> > 
> > We shouldn't use the URL for this, the blocklist should be the same
> > regardless of the device/os/etc.
> 
> I'll let somebody from mobile comment on that.

By which I mean, if we need to do that then we should extend the blocklist xml format to support it so the blocklist.xml we ship with the app does the right thing regardless of the device you use it with.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.