Closed Bug 495741 Opened 15 years ago Closed 15 years ago

Upgrade to Flashblock 1.5.10

Categories

(Camino Graveyard :: Annoyance Blocking, defect)

All
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alqahira, Assigned: alqahira)

Details

Attachments

(1 file)

There have been two releases of Flashblock since our last upgrade; one that included the fixes we took, plus the fix for https://www.mozdev.org/bugs/show_bug.cgi?id=20678 which came right after our pull, and one that fixed something related to the XUL context menus and thus shouldn't apply to us.

We probably want to pick up the fix for https://www.mozdev.org/bugs/show_bug.cgi?id=20678 sooner rather than later, but I'm not sure if we want to do it at this point before b3 and 1.6.8.
Flags: camino2.0b3?
Flags: camino1.6.8?
I'd say let's definitely go ahead for b3; I'm more hesitant about 1.6.8.
I've done minimal testing on this (basically testcases in bugs on file in our cvs log, plus the testcase in aforementioned Flashblock bug), and nothing seems untoward :)
Assignee: nobody → alqahira
Status: NEW → ASSIGNED
Attachment #380870 - Flags: superreview?(stuart.morgan+bugzilla)
Comment on attachment 380870 [details] [diff] [review]
Upgrade to 1.5.10

sr=smorgan
Attachment #380870 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
Landed on cvs trunk in advance of 2.0b3.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Consensus seems to be we'll take this for 1.6.9.
Flags: camino2.0b3?
Flags: camino2.0b3+
Flags: camino1.6.8?
Flags: camino1.6.8-
We'll take 1.5.11 instead, bug 506420.
Flags: camino1.6.9? → camino1.6.9-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: