Closed
Bug 246131
Opened 20 years ago
Closed 12 years ago
Indicator/dialog for blocked XPIs
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: cilias, Unassigned)
References
Details
With bug 240552 in effect, the there is no real indicator to tell users that an XPI has been blocked. To quote bug 240552 comment 56: "So now when someone clicks on, say, http://www.hacksrus.com/~ginda/chatzilla/xpi/chatzilla-0.9.64.xpi then the throbber will briefly spin and... that's all folks." Without knowing about bug 240552, I first thought it was a slow connection, then thought the XPInstall engine was broken. If all 1.7 is going to have concerning bug 240552 is couple of prefs in about:config, there should be some sort of indicator.
Comment 1•20 years ago
|
||
Such an indicator was intended to be part of the UI in bug 241705 *** This bug has been marked as a duplicate of 241705 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•20 years ago
|
||
I'm under the impression that bug 241705 is long term (and assigned to Firefox). If this makes it into 1.7 final (and Netscape 7.2) without any UI, I think users are going to be confused when a XPI is blocked. Will a new larger whitelist be the answer?
Comment 3•20 years ago
|
||
Fair enough, this is a well-defined subset of bug 241705 that could be implemented independently.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•20 years ago
|
Reporter | ||
Comment 4•20 years ago
|
||
I should also add that a simple "Alert" message, with an OK button will do. Something like the alert, when a user enters a URL that cannot be found. The cool UI stuff, like an icon in the bottom corner, can come later in bug 241705.
Reporter | ||
Comment 5•20 years ago
|
||
This bug was originally intended for Mozilla 1.7. Now that Mozilla 1.7 has been released, with xpinstall.whitelist.required set to false, this bug does not apply. However, as Daniel Veditz states in comment 3, this bug works as a subset of bug 241705.
Updated•20 years ago
|
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0?
Updated•20 years ago
|
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0RC1-
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0-
Blocks: 270170
(In reply to comment #3) > Fair enough, this is a well-defined subset of bug 241705 that could be > implemented independently. It would be nice if we could land bug 270443 and bug 270170 early enough before 1.8b to use both of them to fix this bug.
Flags: blocking1.8b?
Updated•20 years ago
|
Flags: blocking1.8b?
Flags: blocking1.8b-
Flags: blocking-aviary1.0PR-
Updated•19 years ago
|
Flags: blocking1.8b4?
Flags: blocking1.8b3?
Comment 7•19 years ago
|
||
This is seamonkey-only, does not block aviary releases.
Assignee: dveditz → guifeatures
Component: Installer: XPInstall Engine → XP Apps: GUI Features
Flags: blocking1.8b4?
Flags: blocking1.8b3?
Product: Core → Mozilla Application Suite
Comment 8•16 years ago
|
||
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: guifeatures
Comment 9•12 years ago
|
||
We now have notification boxes and doorhangers.
Status: NEW → RESOLVED
Closed: 20 years ago → 12 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Updated•12 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•