Closed Bug 412372 Opened 17 years ago Closed 16 years ago

need major update billboard HTML files for Firefox 2 -> Firefox 3 update offer

Categories

(www.mozilla.org :: General, defect, P1)

Product:
www.mozilla.org
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: tchung, Assigned: dbottoms)

References

Details

(Whiteboard: [MU+][server side])

Attachments

(4 files)

major update - without warning
143.03 KB, image/jpeg
beltzner
: review+
Details
major update - with warning
148.40 KB, image/jpeg
Details
New images for major update window
239.62 KB, application/zip
Details
Modified billboard with fewer words in headline
240.45 KB, application/zip
Details 
Tracking bug to update new text for the software update dialog when users migrate from Fx2.0.x -> Fx3.0.x.

Current dialog is placeholder text pulled from the Fx1.5.x->Fx2.0.x bits.
I'll take this.
Assignee: nobody → samuel.sidler
We need the pages corresponding to:

1, http://en-us.www.mozilla.com/en-US/firefox/2.0/details/index.html
for the content for the initial update dialog (the "pitch")

2, http://en-us.www.mozilla.com/en-US/firefox/2.0/eula/index.html
the EULA/license that must be accepted

These are fed into the code that generates the update information for AUS. IIRC, only the first one is localized, but SVN would be the authoritative source for that. 
On top of the URLs changing, are there plans to update the eula text too for fx3?  
This might depend on bug 367913, as it relates to the way we present this information within the update dialog and on a full page.
Depends on: 367913
I'm not currently working on this. The idea I had was very similar to the current one. I'm not sure how many features we want to list given this text needs to be localized.
Assignee: samuel.sidler → nobody
Whiteboard: [MU+] DUPEME?
Whiteboard: [MU+] DUPEME? → [MU+]
(In reply to comment #2)
> We need the pages corresponding to:
> 
> 1, http://en-us.www.mozilla.com/en-US/firefox/2.0/details/index.html
> for the content for the initial update dialog (the "pitch")

John Slater and David Bottoms are driving this work, including generating the creative and co-ordinating the localization effort. They've been asked to have en-US versions completed by July 11th so that l10n can start and have two weekends, with a final delivery date for all content by July 21.

Draft content will be posted here when they've got it. The current thinking is to make it short & sweet, something like:

  Faster.  Safer.  More Awesome.
 .---------------------------.
 |  Update to Firefox 3 Now  |
 '---------------------------'
  (click here to find out more)

> 2, http://en-us.www.mozilla.com/en-US/firefox/2.0/eula/index.html
> the EULA/license that must be accepted

Already done, as per bug 432167

> These are fed into the code that generates the update information for AUS.
> IIRC, only the first one is localized, but SVN would be the authoritative
> source for that. 

That's correct. We don't localize the EULA, or at least, haven't in the past.
Assignee: nobody → dbottoms
Summary: Software Update dialog window needs text update for Fx2->Fx3 → need major update billboard HTML files for Firefox 2 -> Firefox 3 update offer

    
    

    
  
Hi all. I just attached our proposed mockups for the major update page - one with the add-ons compatibility warning and one without. We structured it so the key info is always above the fold, and the secondary info is potentially below it...either way the main message is there, though.

David R, David B and I all feel good about it, but let us know what you think.

Our only suggested change at this point is to move the "learn more" link over to the right so it doesn't compete with the FF3 wordmark. But, we're certainly open to additional feedback if anyone has any.

Once the issue about the sizing of the box has been resolved it should be pretty easy for us to finalize this and hand it over. Just keep us posted...

    
    

    
  
Those both look good to me.

One note: While you're working on this update, it might be useful to create a second major update warning, specifically for after we sunset Firefox 2. If we do it now, instead of at the last minute later, it'll give localizers time to translate that page as well. I know that's six months out, but better now than later. :)

    
    

    
  
One note from the localizers point of view. Please remember that some locales need a lot of space for this text. Personally I believe that I'll even have a problem with the German translation. It would be "Aktualisieren Sie jetzt auf den bisher besten Firefox". As you see this will give ugly scroll bars or even hide some of the content.

Pascal, what is your feeling about? I cannot remember if we had problems with the length of the major upgrade text for Firefox 2.

    
    

    
  
(In reply to comment #12)
> One note from the localizers point of view. Please remember that some locales
> need a lot of space for this text. Personally I believe that I'll even have a
> problem with the German translation. It would be "Aktualisieren Sie jetzt auf
> den bisher besten Firefox". As you see this will give ugly scroll bars or even
> hide some of the content.
That's a great point, and certainly very important to consider. I haven't done an exact word count comparison, but at a quick glance the 'above the fold' content of this version actually seems to have a significantly smaller number of words than the previous version.

One possible solution: the headline of this en-US version is pretty big. While that's certainly preferable, I think it would be very acceptable as a plan B to shrink the font size for languages that need the extra space. Would that work?


    
    

    
  
what will be the exact pixel size of the box? In the second version there is a warning message with a button and a keybinding to this button, is this button an HTML button or a XUL one? Is there actual html/css code somewhere to do l10n tests?

I don't really see why we have a big firefox logo there, the user is already a Firefox user so he knows that he is updating Firefox, the main information is that he is upgrading to version 3, so the number should be prominent in my opinion. Many people know that they use a software but don't know what version they have.

I agree with Henrik that the title is going to be significantly longer in other languages, words like "update" or "upgrade" are often replaced by a sentence, the adjective and adverb used in the title are also likely to be much longer in other locales, there definitely is a space problem for the title with the current wording. "Upgrade to Firefox 3" would be a better title I think.



    
    

    
  


  
Here are the latest images. Please confirm that the sizing (based on the previous comments) is correct.  Also, please confirm that the centered-justified layout is acceptable.  

I'd also like to make sure this entire window is clickable (and not just the link).

    
    

    
  
It's still hard to say if everything will fit into the box for each locale. Pascal, AFAIR we had a nice sandbox where we were able to play with for the major upgrade from Firefox 1.5 to 2. Could this be re-used? I believe that it will make our life much easier.

    
    

    
  
(In reply to comment #14)
> other locales, there definitely is a space problem for the title with the
> current wording. "Upgrade to Firefox 3" would be a better title I think.

The text outside the image will already advertise Firefox 3.   See https://bugzilla.mozilla.org/attachment.cgi?id=328969

"You can download Bon Echo 3.0 Now!"

I sincerely hope the bon echo gets replaced by "Firefox".  Same for the Bon Echo icon in that upper left hand corner, to be a firefox icon.



    
    

    
  


  
OK, here's a revised version with the suggested headline "Upgrade to Firefox 3!" for better localization.  Please let me know if this will satisfy localization requirements.

    
    

    
  
Is this bug appropriate for localization or should a new bug be started?

    
    

    
  
#16, henrik, I intend to reuse the testing field I had created for the previous major update, yes

#19, yes, a new bug should be startesd as soon as we are sure that the referencen content is final

    
    

    
  
(In reply to comment #20)
> #16, henrik, I intend to reuse the testing field I had created for the previous
> major update, yes

Pascal, do you have these older ones still online, so we could have a look at? I believe that will help to find the final content. In most cases you have to see a special locale to get in touch with a possible translation and its length.

    
    

    
  
For localization, we need the en-US html source file that will be used in the box.

    
    

    
  
From a design standpoint, are the attached design mockups fine for localization?  

    
    

    
  
yes
Whiteboard: [MU+] → [MU+][server side]

    
    

    
  
OK, let's get cracking!

Steven: what do you need from Dave Bottoms / Rolnitzky in order to turn these into HTML snippets with variable width layouts? It looks like the design will be some background graphics, a firefox logo, a firefox wordmark, and some text (in HTML)

Pascal: can you start the localizers on the text ASAP? looks like we'll need:

 Upgrade to Firefox 3!
 Learn more.
 Thousands of improvements.
 Faster. Safer. Smarter.
 More awesome than ever.

Since we're no longer looking at a string freeze for 3.1b1 this Friday, perhaps we can get the localizers to focus on this for now to get it out of the way?
Severity: normal → major
Priority: -- → P1

    
    

    
  
Comment on attachment 328969 [details]
major update - without warning

for formality's sake, r+=beltzner

We'll want to build things such that the bit at the top it centered and anchored to the top. The bit at the bottom should be centered and anchored to the bottom. That way if the size of the dialog changes, we should be ok.

        Attachment #328969 -
        Flags: review+

    
    

    
  
The only thing I need to start localization is the final html that will be used, as soon as I have this, we can start translating. I would also need to know the inner size of the content box so as to test all locales and make sure the text is not rendering outside of the box.

    
    

    
  
Who's building the actual, final HTML? Steven Garrity? Let's get this moving asap.

    
    

    
  
I'll try to get to this over the weekend. Is Monday too late?

    
    

    
  
(In reply to comment #28)
> The only thing I need to start localization is the final html that will be
> used, as soon as I have this, we can start translating. I would also need to

Why do you need this? Can you not get the localizers started on the text itself? We should parallelize this as much as possible.

> know the inner size of the content box so as to test all locales and make sure
> the text is not rendering outside of the box.

As you know, the inner size of that box depends on the locale. The mockups you're seeing here are based on the en-US dimensions, but in some locales the dialog is wider.

    
    

    
  
(In reply to comment #30)
> I'll try to get to this over the weekend. Is Monday too late?

Monday morning should be fine. Ping me (email or phone) if you need help/advice.


    
    

    
  
>Why do you need this? Can you not get the localizers started on the text
itself? We should parallelize this as much as possible.

Yes, it can be done by translating the strings only, but then I will have to script the creation of pages instead of giving 10 lines of html source to the localizers. I had a process in mind when I asked for the source 1 month ago, I can change it but if we have the html on Monday you will only win 24h/48h of localization at best. When is the update message going to be launched?

    
    

    
  
I was under the impression that a lot of localizers worked only on weekends; if we're just talking about a 24hr gain, then yes, let's wait for the HTML.

    
    

    
  
>I was under the impression that a lot of localizers worked only on weekends; if
we're just talking about a 24hr gain, then yes, let's wait for the HTML.

This is true during the year but now in August which is summer break.

    
    

    
  
Checked in a first go a the HTML version of the English translation (r17711).

https://www-trunk.stage.mozilla.com/en-US/firefox/3.0.1/details/

Let me know of any changes required. Pascal - let me know if there are any localization issues with the markup/css.

    
    

    
  
The "3" in the Firefox 3 wordmark looks a little cut off on the right hand side.

    
    

    
  
the bullet points drawn with an image will need an alternative css for RTL because it is positionned on the right. I don't think it's worth using an image since it's just a small square, we could probably obtain the same result with list-style-type and it wouldn't require a specail rtl version but I let you judge on this.

The html is fine for me, if everybody is ok for the text, I am going to prepare the task to give it to localizers.

    
    

    
  
the url (https://www-trunk.stage.mozilla.com/en-US/firefox/3.0.1/details/) is at 3.0.1, shouldn't it be at 3.0.2? I guess that we will offer the major update with or after the 3.0.2 minor update right ?

    
    

    
  
(In reply to comment #39)
> the url (https://www-trunk.stage.mozilla.com/en-US/firefox/3.0.1/details/) is
> at 3.0.1, shouldn't it be at 3.0.2? I guess that we will offer the major update
> with or after the 3.0.2 minor update right ?

No, MU is going out with 3.0.1 (as in, end of this week, early next week at latest). 3.0.2 hasn't even been built.

    
    

    
  
IMO it doesn't make sense, first it is not possible to have the box ready in 50 locales in a week in the middle of summer when many localizers are probably on summer holidays and second I don't think it will be a good user experience to be proposed an update to 3.0.2 like a week after they have installed 3.0.2. I'll do my best to have as many locales as possible, but why not offering an upgrade to 3.0.2 ?

    
    

    
  
(In reply to comment #41)
> IMO it doesn't make sense, first it is not possible to have the box ready in 50
> locales in a week in the middle of summer when many localizers are probably on
> summer holidays and second I don't think it will be a good user experience to
> be proposed an update to 3.0.2 like a week after they have installed 3.0.2.
> I'll do my best to have as many locales as possible, but why not offering an
> upgrade to 3.0.2 ?
> 

Unfortunately, its a carefully assessed business decision here, that we need MU out as fast as possible.  Can't speak for the 50 locales point you make, but there's also a handful of MU bugs that users wont be getting until 3.0.2.  It's a risk we're gonna be taking, but seems to have even more serious implications if we dont MU now.   From QA perspective, i agree with your opinions too, but hey... gotta roll with what's best for Mozilla.  

    
    

    
  
(In reply to comment #37)
> The "3" in the Firefox 3 wordmark looks a little cut off on the right hand
> side.

Good catch - will fix (I'll also fix the blue showing behind the white-gradient box.

Pascal, I'll address the rtl-bullet issue as well.

    
    

    
  
(In reply to comment #37)
> The "3" in the Firefox 3 wordmark looks a little cut off on the right hand
> side.

Fixed in r17762.


(In reply to comment #38)
> the bullet points drawn with an image will need an alternative css for RTL
> because it is positionned on the right. I don't think it's worth using an image
> since it's just a small square, we could probably obtain the same result with
> list-style-type and it wouldn't require a specail rtl version but I let you
> judge on this.

Fixed in r17761 for the entire site rather than just this page. Since the graphic is just a simple square, I just needed to adjust it's position via CSS when the page is RTL.

    
    

    
  
what is the size in pixels of the frame in the upgrade box where the web page will be shown ?

    
    

    
  
Steven: should the "Learn More" link not be target="_blank"? Don't want it opening up in the wee browser window in the MU offer dialog :)

    
    

    
  
(In reply to comment #46)
> Steven: should the "Learn More" link not be target="_blank"? Don't want it
> opening up in the wee browser window in the MU offer dialog :)

I can add target="_blank", but that's not valid XHTML. Any other ways to achieve that?

    
    

    
  
Yesterday I added target="_blank" on all locales including en-US but excepting Japanese as it is on mozilla.jp, I'll ping Kohei about it. I also filled in the  lang attributes for all locales so as to be able to send specific css rules per locale from update.css

The screenshots from Tomcat during QA show that on XP, the dimensions of the box for a 36em window is 336x196px. You can see on http://img102.imageshack.us/my.php?image=pascal1li0.jpg that even English is too tall and we have a vertical scrollbar.

Personnally I think that the logo and "firefox 3" wordmark below are useless graphics element, if the user is using Firefox, he doesn't need to be reminded what our logo is in an upgrade box, if we want to keep the logo somewhere we could just have it like a faint background image for example. This way there would be much more room for content and the "Upgrade to Firefox 3" string would not be on two lines, that would probably solve the overflowing problem for most, if not all, locales.

    
    

    
  
We use Firefox branding at every user touchpoint (first-run, download page, update page, etc.) to reinforce the Firefox brand.  We're battling against muscle memory and users clicking on the blue e all the time.  Visually, using the logo/wordmark ties this touchpoint to all others.  If the user is using Firefox they do get this update -- but not all of them are Firefox power-users -- they may use Firefox very infrequently.

Slater might have another opinion, but I think it makes complete sense to leave these two in the box in some form. Maybe the logo/wordmark can be sized smaller still to prevent two line wrapping or at least the scrollbars, or maybe background works as you suggest, but I think they should be there.  

    
    

    
  
I agree with David. The logo really needs to be in there for all the reasons he said. I think having the "upgrade to Firefox 3" text wrap around to two lines is pretty much unavoidable, but maybe we can shrink the logo down a little bit so there's not a vertical scroll bar. 

Overall, though, I don't think this is all that crucial of an issue...the main message of upgrading comes through no matter what.

    
    

    
  
We don't need to shrink the logo down to avoid the scrollbar (at least in en-US). I've made a few minor spacing adjustments in r17871 that should eliminate the vertical scrollbar (please confirm).

Pascal, let me know if any locales need more room.
Depends on: 451807
Depends on: 451808
Depends on: 451830
No longer depends on: 367913

    
    

    
  
This was fixed a long time ago.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: