Where possible, remove the possibility of other components breaking app update

RESOLVED FIXED in mozilla2.0b10

Status

()

Toolkit
Application Update
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: rstrong, Assigned: rstrong)

Tracking

Trunk
mozilla2.0b10
Points:
---
Bug Flags:
in-testsuite -
in-litmus -

Firefox Tracking Flags

(blocking2.0 -, status1.9.2 unaffected, status1.9.1 unaffected)

Details

Attachments

(1 attachment)

Spinoff of bug 590978
note: Bug 595455 added fallback to prompt the user to manually update if update checks are repeatedly failing.
Created attachment 502990 [details] [diff] [review]
patch rev1

This should take care of the common failure cases such as bug 621660
Assignee: nobody → robert.bugzilla
Status: NEW → ASSIGNED
Attachment #502990 - Flags: review?(dtownsend)
Comment on attachment 502990 [details] [diff] [review]
patch rev1

bah... forgot one more thing
Attachment #502990 - Attachment is obsolete: true
Attachment #502990 - Flags: review?(dtownsend)
Comment on attachment 502990 [details] [diff] [review]
patch rev1

Let's just go with this as is
Attachment #502990 - Attachment is obsolete: false
Attachment #502990 - Flags: review?(dtownsend)
I'd like this to be a softblocker so requesting blocking.
blocking2.0: --- → ?
(In reply to comment #5)
> I'd like this to be a softblocker so requesting blocking.

This problem occurs with incompat addons doing stupid things AND claiming to be compat -- can't block on it BUT BUT BUT - find us on IRC, we'll approve this in a heartbeat.
blocking2.0: ? → -
Attachment #502990 - Flags: review?(dtownsend) → review+
Attachment #502990 - Flags: approval2.0+
Pushed to mozilla-central
http://hg.mozilla.org/mozilla-central/rev/fe1ce4c8c5cf
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
status1.9.1: --- → unaffected
status1.9.2: --- → unaffected
Flags: in-testsuite-
Flags: in-litmus-
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b10
You need to log in before you can comment on or make changes to this bug.