Closed Bug 593366 Opened 14 years ago Closed 14 years ago

Default text for about:home dynamic content

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 4.0b7
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: johnath, Assigned: cbeard)

References

Details

(Whiteboard: [strings][fixed by bug 563738][about-home])

In cases where we can't reach the dynamic content service described in bug {{bug|563738}}, we would still like to use the dynamic content area of about:home to display *some* message. This bug tracks the creation and addition of that message.

This needs to be done in the next week to make string freeze. Beard suggested he could provide something here, so assigning this to him for the moment, though Marco will likely write the patch.
This smells like it should be part of our B6 strings blockers, right?
blocking2.0: --- → ?
Whiteboard: [strings]
Blocks: 563738
I need this for bug 563738, since I'll most likely have to put that string in a dtd file.
blocking2.0: ? → beta6+
Chris: we need this by EOD tomorrow, please.
Here is the default text for the Start Page.  Chris mentioned that even for the default text we could alter between 2 different snippets so we've provided 2.  However, if there can be only one snippet then please use the first one.  Note for the first one the link currently doesn't work so we'll have to either redirect the link and/or change the link later on when we switch from the Beta features page to the final release features page.  

Thanks for choosing Firefox! To get the most out of your browser, learn more about the latest features. ["latest features" text should link to "http://www.mozilla.com/firefox/4.0/features"]


It's easy to customize your Firefox exactly the way you want it. Choose from thousands of add-ons. ["Choose from thousands of add-ons" text should link to "https://addons.mozilla.org/firefox/?browse=featured]
I see a gap to bridge between comment 4 here and bug 563738 comment 20, there we have one single html fragment, and here we have two wiki formatted strings. beltzner and I talked about the snippet content in the l10n context earlier today, he offered to open that thread offline. Maybe this gap is part of that?
I suspect taking simple strings for the default values, rather than complicated html/js fragments, would be easier since those are going into a dtd file?
In my personal opinion it boils down to whether the rotation logic for snippets lives inside about:home or within the snippet from the web, or some default in about:home, but possibly more in the snippet or so.

For l10n of the initial built-in snippet, one static string is easiest. If we're doing a link we can probably segment the text into &snippetphrase.start;<a>&snippetphrase.link;</a>&snippetphrase.end; or so. If we do multiple links, the order might change and things get more complex quickly. Same for multiple phrases.
can't we put the link in an entity and refer to it later so it can have any position? like

defaultSnippet.link = <a href="xyz">link</a>
defaultSnipper.text = this is a &defaultSnippet.link;
I'd rather not have the <a href="..."> and the </a> in l10n if possible. That's just stuff to break. If we do, we can just go for a single defaultSnippet entity altogether, too.

That said, I'm not sure if we actually need to figure out the implementation details to that detail until we know what we're actually supposed to do.
(In reply to comment #5)
> I see a gap to bridge between comment 4 here and bug 563738 comment 20, there
> we have one single html fragment, and here we have two wiki formatted strings.
> beltzner and I talked about the snippet content in the l10n context earlier
> today, he offered to open that thread offline. Maybe this gap is part of that?

Mayumi is using shorthand. I promise promise promise that bug 563738 comment 20 rules the day. A blob of HTML is what gets served to us as dynamic content. If we do something clever with the default content, per Mayumi's question about 2 options, that is special casing which we can do in the default case, but which is not part of the spec'd "dynamic content" handling generally.
I've posted an updated patch in bug 563738 using the strings in comment 4.
Whiteboard: [strings] → [strings][fixed by bug 563738]
Depends on: 594978
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b6
Whiteboard: [strings][fixed by bug 563738] → [strings][fixed by bug 563738][about-home]
You need to log in before you can comment on or make changes to this bug.