Closed
Bug 337823
Opened 19 years ago
Closed 18 years ago
Help -> Release Notes doesn't use url from brand.dtd
Categories
(Firefox :: Menus, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 348076
Firefox 2 beta2
People
(Reporter: steffen.wilberg, Assigned: steffen.wilberg)
Details
Attachments
(1 file)
3.91 KB,
patch
|
mconnor
:
review-
|
Details | Diff | Splinter Review |
Help -> Release Notes calls openReleaseNotes(), which uses releaseNotesURL from region.properties, which is http://www.mozilla.org/products/firefox/releases/%S.html:
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/base/content/utilityOverlay.js&rev=1.32.2.5&mark=435-442#428
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/locales/en-US/chrome/browser-region/region.properties&rev=1.9.2.3&mark=6
On the other hand, about: uses releaseBaseURL from brand.dtd, which is either http://www.mozilla.org/projects/bonecho/releases/__MOZ_APP_VERSION__.html or
http://www.mozilla.com/firefox/releases/__MOZ_APP_VERSION__.html, depending on whether official branding is enabled or not:
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/toolkit/content/about.xhtml&rev=1.8.8.2&mark=82#82
http://lxr.mozilla.org/mozilla1.8/source/browser/locales/en-US/chrome/branding/brand.dtd#6
http://lxr.mozilla.org/mozilla1.8/source/other-licenses/branding/firefox/locales/en-US/brand.dtd#6
This divergence already caused bug 337818.
So Help -> Release Notes should use the releaseBaseURL from brand.dtd.
Assignee | ||
Comment 1•19 years ago
|
||
Similar to bug 337834, but more elegant since it gets rid of openReleaseNotes() and releaseNotesURL, which aren't used anywhere else:
http://lxr.mozilla.org/mozilla1.8/search?string=openReleaseNotes
http://lxr.mozilla.org/mozilla1.8/search?string=releaseNotesURL
Assignee: nobody → steffen.wilberg
Status: NEW → ASSIGNED
Attachment #221908 -
Flags: review?(mconnor)
Attachment #221908 -
Flags: approval-branch-1.8.1?(mconnor)
Comment 2•19 years ago
|
||
*** Bug 337834 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•19 years ago
|
Flags: blocking-firefox2?
Target Milestone: --- → Firefox 2 alpha3
Updated•19 years ago
|
Flags: blocking-firefox2? → blocking-firefox2+
Comment 3•19 years ago
|
||
Comment on attachment 221908 [details] [diff] [review]
patch
So, I don't think the right fix here is to hardcode the URL into content. Its better to include releaseBaseURL into the localized string and expand that.
Attachment #221908 -
Flags: review?(mconnor)
Attachment #221908 -
Flags: review-
Attachment #221908 -
Flags: approval-branch-1.8.1?(mconnor)
Assignee | ||
Comment 4•19 years ago
|
||
I don't understand. What part of the url is hardcoded? &releaseBaseURL; is an entity from brand.dtd and MOZ_APP_VERSION is expanded by the preprocessor. The only fixed part is ".html".
And what do you mean by "include releaseBaseURL into the localized string and expand that"? Pass releaseBaseURL as an argument to openReleaseNotes(), which appends nsIXULAppInfo.version and ".html" to it? How does that make a difference? It just moves code from content/baseMenuOverlay.xul to content/utilityOverlay.js. And it queries the app version each time despite the fact that it can't change since it's already hardcoded in nsBrowserApp.cpp.
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/app/nsBrowserApp.cpp&rev=1.31.2.3&mark=51#46
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/app/Makefile.in&rev=1.85.2.6&mark=172,173#172
I did the same to about.xhtml in bug 318991 and bsmedberg liked it a lot.
Comment 5•19 years ago
|
||
If this can get resolved for beta fine, for now we'll go with the less elegant fix.
Flags: blocking-firefox2+ → blocking-firefox2-
Assignee | ||
Comment 6•19 years ago
|
||
Since nobody bothered to check in beltzner's fix from bug 337834 (or answer my questions in comment 4), this hit us again for alpha 3. I've reopened bug 337818 to add another server redirect.
Target Milestone: Firefox 2 alpha3 → Firefox 2 beta1
Comment 7•19 years ago
|
||
renominating for beta1 so we don't get screwed; it's either a patch like the one offered here, or a less elegant solution as offered in attachment 221901 [details] [diff] [review]
Flags: blocking-firefox2- → blocking-firefox2?
Updated•19 years ago
|
Flags: blocking-firefox2? → blocking-firefox2+
Updated•19 years ago
|
Whiteboard: 181b1+
Updated•19 years ago
|
Whiteboard: 181b1+
Updated•19 years ago
|
Target Milestone: Firefox 2 beta1 → Firefox 2 beta2
Comment 9•19 years ago
|
||
Not going to block on this, negative side is that we have to keep URLs in sync, but we can live with that.
Flags: blocking-firefox2+ → blocking-firefox2-
Whiteboard: [at risk]
Assignee | ||
Comment 10•18 years ago
|
||
Fixed by bug 348076.
*** This bug has been marked as a duplicate of 348076 ***
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•