Closed
Bug 563168
Opened 15 years ago
Closed 15 years ago
Blocklist service warns of bad add-ons, but nothing is listed.
Categories
(Toolkit :: Add-ons Manager, defect, P1)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla1.9.3a5
People
(Reporter: KWierso, Assigned: mossop)
References
()
Details
(Whiteboard: [rewrite])
Attachments
(1 file)
8.97 KB,
patch
|
robert.strong.bugs
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100501 Minefield/3.7a5pre RTSE/1.2.0.20100406
Build Identifier:
I'm using one of the recent trunk nightlies with the new Extension Manager stuff.
I just had the Blocklist warning box pop up, saying that some of my add-ons are
known to cause stability or security problems.
But the list was empty.
Looking at the actual list( https://www.mozilla.com/en-US/blocklist/ ), I think
my version of the Java Deployment Toolkit actually is in the blocklist, but the
warning for bad add-ons was empty.
After Restarting Firefox, it doesn't look like anything was actually disabled.
Reproducible: Always
Reporter | ||
Comment 1•15 years ago
|
||
It has now come up twice for me.
I'm not sure what steps to reproduce.
Comment 2•15 years ago
|
||
Have seen the same problem last week but forgot to file it. Easy steps to reproduce are:
1. Install the Viewpoint Media Player plugin (see URL)
2. Wait a while or trigger the blocklisting check
Blocks: 461973
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86 → All
Version: unspecified → Trunk
Assignee | ||
Updated•15 years ago
|
Priority: -- → P1
Assignee | ||
Comment 3•15 years ago
|
||
Should have tested this properly with the new UI. The blocklist dialog uses some bindings that used to be in extensions.xml that got removed. The testcase verifies that the dialog is loaded and the correct things passed, but not that the UI displays correctly.
http://hg.mozilla.org/projects/addonsmgr/rev/8f225766b6db
Flags: in-testsuite?
Flags: in-litmus?
Whiteboard: [rewrite] → [rewrite][fixed-in-addonsmgr][needs-review]
Assignee | ||
Comment 4•15 years ago
|
||
This pulls the necessary bindings into a new file (removing the unnecessary addon-name-version).
Also copies across the old needed entities. I don't think we need to rename these as they are in a new file but need to check that.
Assignee: nobody → dtownsend
Status: NEW → ASSIGNED
Attachment #443762 -
Flags: review?(robert.bugzilla)
![]() |
||
Comment 5•15 years ago
|
||
Comment on attachment 443762 [details] [diff] [review]
patch rev 1
If there is a need to change the entity names in this case then IMO the process is borked! r=me
Attachment #443762 -
Flags: review?(robert.bugzilla) → review+
![]() |
||
Updated•15 years ago
|
Whiteboard: [rewrite][fixed-in-addonsmgr][needs-review] → [rewrite][fixed-in-addonsmgr][needs-landing]
Assignee | ||
Comment 6•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [rewrite][fixed-in-addonsmgr][needs-landing] → [rewrite]
Target Milestone: --- → mozilla1.9.3a5
Comment 7•15 years ago
|
||
Verified fixed with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100514 Minefield/3.7a5pre
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Flags: in-litmus? → in-litmus?(vlad.maniac)
Assignee | ||
Comment 8•14 years ago
|
||
I think we can cover this automatically but I think we should have a manual test of the blocklist too if we don't already have one.
Comment 9•14 years ago
|
||
(In reply to comment #8)
> I think we can cover this automatically but I think we should have a manual
> test of the blocklist too if we don't already have one.
Right now we only have a test for installing an blocklisted extension. I would assume it will be enough the blocklist for extensions? If that's fine I will create a similar test like https://litmus.mozilla.org/show_test.cgi?id=10853
Assignee | ||
Comment 10•14 years ago
|
||
(In reply to comment #9)
> (In reply to comment #8)
> > I think we can cover this automatically but I think we should have a manual
> > test of the blocklist too if we don't already have one.
>
> Right now we only have a test for installing an blocklisted extension. I would
> assume it will be enough the blocklist for extensions? If that's fine I will
> create a similar test like https://litmus.mozilla.org/show_test.cgi?id=10853
Yes that should be fine.
Comment 11•14 years ago
|
||
Litmus test has been added:
https://litmus.mozilla.org/show_test.cgi?id=15309
Flags: in-litmus?(vlad.maniac) → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•