Closed
Bug 393285
Opened 19 years ago
Closed 18 years ago
Add OS and ABI for restricting the blocklist checks
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla1.9beta2
People
(Reporter: robert.strong.bugs, Assigned: mossop)
References
Details
Attachments
(3 files)
|
3.12 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
|
6.60 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
|
3.11 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
So we could match a plugin file name based on OS, etc.
| Reporter | ||
Comment 1•19 years ago
|
||
We also need to only provide the option to update a plugin when an update to the plugin is available (UI work for this to be done in bug 391714).
| Assignee | ||
Comment 2•18 years ago
|
||
This would be needed to block plugins only on certain platforms
Flags: blocking-firefox3?
Updated•18 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Updated•18 years ago
|
Target Milestone: --- → Firefox 3 M10
| Assignee | ||
Comment 3•18 years ago
|
||
Rob, did you have any thoughts on how this would fit into the schema? I'm currently thinking of just an os and abi attribute on the pluginItem tag containing a comma separated list to match against.
I dont think we need regex's for this since these values should be well defined. We also might want to add it to the emItem as well to cover add-ons.
Assignee: nobody → dtownsend
| Reporter | ||
Comment 4•18 years ago
|
||
That's what I was thinking on all points. I have some vague concerns about the implementation details and uniqueness but any issues like that should be sorted during the implementation. Note: the reason for ABI mainly came to mind do to x64, etc.
| Assignee | ||
Comment 5•18 years ago
|
||
This is a pretty simple fix, just ignore any emItem or pluginItem elements that match the os and/or xpcomabi check.
| Assignee | ||
Comment 6•18 years ago
|
||
This is a set of unit tests for blocklisting. It is only really feasible to test the add-ons side of the blocklist service unfortunately. These testcases however won't work without either the next attachment or getting bug 319968 fixed (I'd prefer the latter)
| Assignee | ||
Comment 7•18 years ago
|
||
This removes any use of classinfo from the blocklist service, necessary for unit tests to work without bug 319968 being fixed.
| Assignee | ||
Updated•18 years ago
|
Attachment #284634 -
Flags: review?(robert.bugzilla)
| Reporter | ||
Updated•18 years ago
|
Attachment #284634 -
Flags: review?(robert.bugzilla) → review+
| Reporter | ||
Comment 8•18 years ago
|
||
Comment on attachment 284636 [details] [diff] [review]
classinfo fixes
I'm fine with waiting on bug 319968 or going with the classinfo fixes so +'ing and I'll let you decide if you want to wait.
Attachment #284636 -
Flags: review+
| Assignee | ||
Updated•18 years ago
|
Whiteboard: [has patch][has reviews]
| Assignee | ||
Updated•18 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 9•18 years ago
|
||
Comment on attachment 284635 [details] [diff] [review]
unit tests rev 1
Rob, can you just confirm you're ok with this.
Attachment #284635 -
Flags: review?(robert.bugzilla)
| Assignee | ||
Updated•18 years ago
|
Whiteboard: [has patch][has reviews] → [has patch][has reviews] unit tests require bug 319968
| Reporter | ||
Comment 10•18 years ago
|
||
Comment on attachment 284635 [details] [diff] [review]
unit tests rev 1
Looks fine and thanks Dave.
Attachment #284635 -
Flags: review?(robert.bugzilla) → review+
Updated•18 years ago
|
Keywords: checkin-needed
Comment 11•18 years ago
|
||
main patch:
Checking in toolkit/mozapps/extensions/src/nsBlocklistService.js;
/cvsroot/mozilla/toolkit/mozapps/extensions/src/nsBlocklistService.js,v <-- nsBlocklistService.js
new revision: 1.7; previous revision: 1.6
done
classinfo fixes:
Checking in toolkit/mozapps/extensions/src/nsBlocklistService.js;
/cvsroot/mozilla/toolkit/mozapps/extensions/src/nsBlocklistService.js,v <-- nsBlocklistService.js
new revision: 1.8; previous revision: 1.7
done
unit tests:
RCS file: /cvsroot/mozilla/toolkit/mozapps/extensions/test/unit/data/test_bug393285.xml,v
done
Checking in toolkit/mozapps/extensions/test/unit/data/test_bug393285.xml;
/cvsroot/mozilla/toolkit/mozapps/extensions/test/unit/data/test_bug393285.xml,v <-- test_bug393285.xml
initial revision: 1.1
done
RCS file: /cvsroot/mozilla/toolkit/mozapps/extensions/test/unit/test_bug393285.js,v
done
Checking in toolkit/mozapps/extensions/test/unit/test_bug393285.js;
/cvsroot/mozilla/toolkit/mozapps/extensions/test/unit/test_bug393285.js,v <-- test_bug393285.js
initial revision: 1.1
done
| Assignee | ||
Updated•18 years ago
|
Whiteboard: [has patch][has reviews] unit tests require bug 319968
Comment 12•18 years ago
|
||
Dave, are there any testcases here that QA can verify? Or do the unit tests you added adequate for verification coverage?
| Assignee | ||
Comment 13•18 years ago
|
||
(In reply to comment #12)
> Dave, are there any testcases here that QA can verify? Or do the unit tests
> you added adequate for verification coverage?
The unit tests are I think adequate for the extensions side, Will provide a more thorough blocklist example in bug 391731 for plugins.
Flags: in-testsuite+
Comment 14•18 years ago
|
||
Per the unit tests and the example in bug 391731, im marking this bug verified.
Status: RESOLVED → VERIFIED
Updated•18 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•