Closed
Bug 396536
Opened 18 years ago
Closed 16 years ago
Firefox Japanese: cannot select Google Reader as a feed reader option
Categories
(Mozilla Localizations :: ja / Japanese, defect)
Mozilla Localizations
ja / Japanese
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9.1
People
(Reporter: kohei, Assigned: bugzilla)
Details
(Keywords: fixed1.9.1, jp-critical, productization)
Attachments
(1 file)
1.37 KB,
patch
|
stas
:
review+
|
Details | Diff | Splinter Review |
It's not known exactly when the problem arose, but Google has made some changes on their feed subscription page.
Preview any feed and select Google. For English locale, you can see such a page that shows two options: iGoogle widget and Google Reader.
http://www.google.com/ig/add?feedurl=http%3A%2F%2Fwww.mozilla-japan.org%2Fnews-jp.rdf
But for Japanese locale, we are redirected to this iGoogle personalize page:
http://www.google.com/ig/adde?moduleurl=http://www.mozilla-japan.org/news-jp.rdf
Previously, we have got the same page as English locale. Now, we cannot select Google Reader as a feed reader option.
We should contact Google to have the localized page with two options.
Comment 1•18 years ago
|
||
Also, Google launched Reader in Japanese today (and French, and I heard rumor of Chinese too) so we'll want to cover those as well.
http://googlereader.blogspot.com/2007/09/breaking-up-isnt-hard-to-do.html
http://www.pacificepoch.com/newsstories/106468_0_5_0_M/
Comment 2•18 years ago
|
||
I'll forward this info to my contacts and update the ticket when I have additional information.
Reporter | ||
Comment 3•18 years ago
|
||
This post says they have added more languages...
http://googleblog.blogspot.com/2007/09/google-reader-goes-multilingual.html
Comment 4•17 years ago
|
||
We are seeing the same problem in FX3Beta3.
Comment 6•17 years ago
|
||
Google has identified the source of the redirect issue, and is working on a resolution. When additional information is available (time to resolve, etc.), I'll update the ticket further.
Assignee | ||
Comment 7•17 years ago
|
||
Google will not redirect from below url now and we can select iGoogle widget or Google Reader correctly:
http://www.google.co.jp/ig/add?feedurl=http%3A%2F%2Fblogs.mozilla-japan.org%2Finside%2Ffeed%2F
--> RESOLVED FIXED
But the page is in English, not Japanese
I filed another bug about it: bug 433836
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•17 years ago
|
||
When user is logged off, only iGoogle is provided.
When user is logged in, both iGoogle and Google Reader are provided.
Reopen.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•17 years ago
|
||
Kev, we've done additional testing and the behavior is different if the user is using the en-US FF vs. ja FF. Kohei is referencing behavior of ja FF.
Comment 10•17 years ago
|
||
Kev, any update from Google on this?
Comment 11•17 years ago
|
||
Have requested an update from Google, as well as a request to respond directly in the bug. I understand it's an ongoing issue, and I'm not sure what the best way to escalate it is at this point, as it's a Google product issue, not Fx.
Reporter | ||
Comment 12•16 years ago
|
||
This issue still exists on Google side, very annoying.
A workaround we can do is to change the URL of feed reader to the English page.
http://www.google.com/ig/add?feedurl=http://mozilla.jp/blog/feed/&hl=en
Or, change the URL to use Google Reader. I prefer this option.
http://www.google.com/reader/view/feed/http://mozilla.jp/blog/feed/
Reporter | ||
Updated•16 years ago
|
Assignee: kev → kozawa
Component: RSS Discovery and Preview → ja / Japanese
Product: Firefox → Mozilla Localizations
QA Contact: rss.preview → bugzilla
Target Milestone: --- → mozilla1.9.1
Reporter | ||
Comment 13•16 years ago
|
||
So the patch will look like this:
http://mxr.mozilla.org/l10n-central/source/ja/browser/chrome/browser-region/region.properties#16
http://mxr.mozilla.org/l10n-central/source/ja-JP-mac/browser/chrome/browser-region/region.properties#16
-browser.contentHandlers.types.0.title = Google
-browser.contentHandlers.types.0.uri = http://www.google.co.jp/ig/add?feedurl=%s
+browser.contentHandlers.types.0.title = Google リーダー
+browser.contentHandlers.types.0.uri = http://www.google.com/reader/view/feed/%s
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 14•16 years ago
|
||
That is:
1. We want Google fix this problem
but if it will not be fixed:
2. We want to change from iGoogle to Google Reader
Comment 15•16 years ago
|
||
I've asked our contacts on PSO about it, and will also try to contact members of the reader team to see if they can work with the search team to address this.
Is there a region-specific reason why we're using that URL (http://www.google.co.jp/ig/add?feedurl=%s
)? The "ig" makes me think the behaviour might actually be expected.
I've noticed other localizations use http://fusion.google.com/add?feedurl=%s.
Adding Staś for his feedback/comment.
Comment 16•16 years ago
|
||
disregard last. doesn't matter if you use fusion, you still get redirected to the iGoogle only page. I'll see if I can get an update from Google.
Assignee | ||
Comment 17•16 years ago
|
||
Thanks working for this, Kev.
We should solve this problem in the next release. So we'll
1. when google response to this until Fx3.1b4 freeze, keep using fusion
2. in case not, we'll change to Google Reader
I'll request approval for this when we cannot get response from google.
Assignee | ||
Comment 18•16 years ago
|
||
Fx3.5b4 code freeze is coming but no response from google.
So, we'll stop using fusion and set to Google Reader.
I'll attach a patch for region.properties and request approval to commit it.
Assignee | ||
Comment 19•16 years ago
|
||
This is the patch to change default rss reader.
Requesting approval to change region.properties.
Assignee: kozawa → bugzilla
Attachment #372022 -
Flags: review?(l10n)
Assignee | ||
Comment 20•16 years ago
|
||
Summary: Google fusion (Google Reader/iGoogle selector page) for ja is broken.
We cannot select google reader when we logged into Google.
We tried to be fixed this problem by google person but couldn't.
So, we'll use Google Reader as a default RSS reader.
Axel, please give approval to change region.properites for ja (ja-JP-mac too).
If you're not the person who can approval, tell us whom should request approval or just change reviewer flag.
Thanks.
Updated•16 years ago
|
Attachment #372022 -
Flags: review?(l10n) → review?(stas)
Comment 21•16 years ago
|
||
Comment on attachment 372022 [details] [diff] [review]
change default rss reader from (broken) google fusion to google reader
Kev, holler if you disagree?
Due to holidays, it might be next week until we get to this.
Reviews for search and friends should go to stas these days.
Reporter | ||
Updated•16 years ago
|
Keywords: productization
Comment 22•16 years ago
|
||
No disagreement. Google has indicated they hope to have a fix for the end of q2, but I'm inclined to change it back when it's in place, not wait.
Comment 23•16 years ago
|
||
Comment on attachment 372022 [details] [diff] [review]
change default rss reader from (broken) google fusion to google reader
r=me. Please land this patch on both branches using a descriptive check-in comment, mentioning the bug number and my review (e.g. "Bug 396536: Cannot select Google Reader as a feed reader option, r=stas").
Please use fixed1.9.1 and verified1.9.1 keywords in this bug to track landing and verification on the 1.9.1 branch.
Attachment #372022 -
Flags: review?(stas) → review+
Comment 24•16 years ago
|
||
(In reply to comment #23)
> r=me. Please land this patch on both branches
Landed to 1.9.1 branch.
What does "both branches" mean? Can I land to 1.9.0?
Keywords: fixed1.9.1
Comment 25•16 years ago
|
||
Thanks!
"Both branches" refers to 1.9.1 and the current trunk, i.e. l10n-central. But you can land it on l10n-central later, it's not required right now for anything. Just please make sure this change is present there when we start working on 3.6 :)
Let's not touch 1.9.0 for this, please :)
Comment 26•16 years ago
|
||
(In reply to comment #24)
> Landed to 1.9.1 branch.
I missed to paste the URL here.
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja/rev/ec80e7f4a3ab
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/ja-JP-mac/rev/cb1ea1d45941
(In reply to comment #25)
> Let's not touch 1.9.0 for this, please :)
I see.
By the way, if a user had used Fx 2.0.0.1 and then updated to 2.0.0.2 -> 2.0.0.x -> 3.0.x -> Shiretoko, the default feed reader is still Yahoo! JAPAN, and the second reader is still (broken) Google fusion.
It's saved in (profiledir)/preferences/existing-profile-defaults.js because of Bug 364297.
How can we care about it?
Reporter | ||
Comment 27•16 years ago
|
||
Confirmed the problem Sakai-san noticed. Is it able to remove the existing-profile-defaults.js when upgrading to 3.5? Yes, some users' default search engine will be forced to change from Y! JAPAN to Google, but we also have to update other search engines anyway (Wikipedia, Oshiete-goo, etc.)
Comment 28•16 years ago
|
||
(In reply to comment #27)
> Is it able to remove the
> existing-profile-defaults.js when upgrading to 3.5?
I don't think we can remove the file, but I guess we can replace it with a new file (or just put a new file if not exists).
http://hg.mozilla.org/releases/mozilla-1.9.1/annotate/674255e22a5f/browser/components/nsBrowserContentHandler.js#l152
If the new file is an empty file, it has same effect as removing file.
> Yes, some users' default
> search engine will be forced to change from Y! JAPAN to Google,
Who can decide whether this is accepted or not?
Assignee | ||
Comment 29•16 years ago
|
||
Since our google reader feed value has already updated I close this bug and filed separate bug 493919 for the problem about default settings for engines/readers/etc.
Thanks.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago → 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•