Closed
Bug 521314
Opened 15 years ago
Closed 15 years ago
Investigate showing a different first-run page
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.1a1
People
(Reporter: kairo, Assigned: kairo)
References
Details
(Keywords: fixed-seamonkey2.0)
Attachments
(2 files)
1.10 KB,
patch
|
neil
:
review+
iannbugzilla
:
approval-seamonkey2.0+
|
Details | Diff | Splinter Review |
1.08 KB,
patch
|
neil
:
review+
iannbugzilla
:
approval-seamonkey2.0+
|
Details | Diff | Splinter Review |
We should think about showing something different than our default homepage as first-run page, e.g. the relnotes.
Flags: wanted-seamonkey2.0?
Yes, would be good.
Flags: wanted-seamonkey2.0? → wanted-seamonkey2.0+
Assignee | ||
Comment 2•15 years ago
|
||
This makes us go to the relnotes on first run (redirects to the "get involved" page for nightlies).
I know this is a locales file, but it doesn't break anyone and if locales don't adapt to it, there's nothing bad that happens, so IMHO it should be OK even with a hard string freeze in place.
Assignee: nobody → kairo
Status: NEW → ASSIGNED
Attachment #405472 -
Flags: review?(neil)
Attachment #405472 -
Flags: approval-seamonkey2.0b2?
Assignee | ||
Comment 3•15 years ago
|
||
Comment on attachment 405472 [details] [diff] [review]
Use relnotes instead
oops, want 2.0 approval, have no time machine around right now to push into beta.
Attachment #405472 -
Flags: approval-seamonkey2.0b2? → approval-seamonkey2.0?
Updated•15 years ago
|
Attachment #405472 -
Flags: review?(neil) → review+
Attachment #405472 -
Flags: approval-seamonkey2.0? → approval-seamonkey2.0+
Assignee | ||
Comment 4•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Keywords: fixed-seamonkey2.0
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1a1
Comment 5•15 years ago
|
||
Hmm, I am now directed to that exact URL on first-run (tried with Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.1.5pre) Gecko/20091014 SeaMonkey/2.0pre), with %VERSION% still as part of the URL! This leads to a 400 Bad Request. Should that not somehow get replaced by the actual version number? Or is there something server-side still missing?
Assignee | ||
Comment 6•15 years ago
|
||
Uh, that doesn't sound good... are we not using the urlformatter like Firefox does?
Assignee | ||
Comment 7•15 years ago
|
||
Right, we don't. reopening. I should have a fix to use the formatter here.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•15 years ago
|
||
This patch makes us use the formatter for this one, I tested it with a profile that correctly ended up with the following output:
Document http://www.seamonkey-project.org/releases/seamonkey2.0pre/ loaded successfully
(and I was correctly redirected to the get-involved page)
Attachment #406341 -
Flags: review?(neil)
Attachment #406341 -
Flags: approval-seamonkey2.0?
Updated•15 years ago
|
Attachment #406341 -
Flags: review?(neil) → review+
Attachment #406341 -
Flags: approval-seamonkey2.0? → approval-seamonkey2.0+
Assignee | ||
Comment 9•15 years ago
|
||
Thanks for the fast r/a, pushed as http://hg.mozilla.org/comm-central/rev/9db84f526a83
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•