Firefox 3.5 marketing banner visible on Dailymotion/JP

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: campbell.zac, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8716703 [details]
fx_3.5.png

This does not seem to be part of any active campaign and the link does not work, but dailymotion.com/jp is showing a headlining banner for downloading Firefox 3.5.

I checked a couple of other dailymotion regions and they don't have this banner.
I've checked about relationship about Mozilla Japan and Dailymotion. We Mozilla Japan don't have any locale specific contact/agreement with Dailymotion. Not sure why they keep the banner only for jp locale but as Zac wrote, the link does not work and should be removed or updated.

in 2009 before the Fx3.5 release, Paul Kim (not MoCo employee now) wrote (in his mail to all@mozilla):
> Tristan Nitot and Paul Rouget connected Mozilla Mountain View with the developers at Dailymotion.com

Paul Rouget, I think you know some relationship with Dailymotion. Can you help us?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(paul)

Comment 2

3 years ago
Wow, that was a very long time ago.
I've contacted someone.
Flags: needinfo?(paul)

Comment 3

3 years ago
Fixed

Comment 4

3 years ago
Thank you Nadir.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Thank Paul and Nadir.

(In reply to nadir.kadem from comment #3)
> Fixed

http://www.dailymotion.com/jp still have Firefox 3.5 banner.
Is that means they'll fix on the next update time?

Comment 6

3 years ago
Hi dynamis,
Can you check again? it should be ok now.

Comment 7

3 years ago
Hi, it seems a cron is setting the skin again, we will have a closer look and tell you when it's ok

Comment 8

3 years ago
fixed for good!
(Reporter)

Comment 9

3 years ago
That seems to have done the trick.
Odd use for a cronjob, I must say..
YES, fixed now. Thanks all!
You need to log in before you can comment on or make changes to this bug.