Extension manager showing incorrect update information.

RESOLVED FIXED in mozilla1.7

Status

()

P3
normal
RESOLVED FIXED
15 years ago
11 years ago

People

(Reporter: spam, Assigned: bugs)

Tracking

unspecified
mozilla1.7
x86
Windows XP
Points:
---
Bug Flags:
blocking1.7 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: fixed-aviary1.0)

Attachments

(2 attachments)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040524 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040524 Firefox/0.8.0+

Just downloaded todays daily Firefox build with the new extension manager, and
tried out buttons (Right after downloading and installing an upgraded version of
TBE) Right after installing and restarting the browser I hit the upgrade button.
There was a window poping up saying that there were no updates available but at
the same time another window popped up saying that there are. 

Reproducible: Always
Steps to Reproduce:
1.Install Tabbrowser extensions
1.Tools --> extensions --> Upgrade

Actual Results:  
Two conflicting messages.

Expected Results:  
Both to say that there are no upgrades available.
(Reporter)

Comment 1

15 years ago
Created attachment 149216 [details]
Screenshot of the bug

Comment 2

15 years ago
Confirmed on same build. Dialog says no updates, biff says updates exist.
block1.0?
Flags: blocking1.0?

Comment 3

15 years ago
Confirming on Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040525
Firefox/0.8.0+

Moving to Software Update and requesting that it blocks 0.9
Status: UNCONFIRMED → NEW
Component: Extension/Theme Manager → Software Update
Ever confirmed: true
Flags: blocking1.0? → blocking0.9?
Status: NEW → ASSIGNED
Flags: blocking0.9? → blocking0.9+
Status: ASSIGNED → RESOLVED
Last Resolved: 15 years ago
Priority: -- → P3
Resolution: --- → FIXED
Target Milestone: --- → Firefox0.9

Updated

15 years ago
Whiteboard: fixed-aviary1.0
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.