Closed Bug 313261 Opened 21 years ago Closed 21 years ago

Installing OSX Firefox stops Safari RSS working

Categories

(Firefox :: Installer, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: markwalker, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 If Firefox (1.0.7 or 1.5b2)is installed without being set as default, it stops Safari 2.0 RSS articles links from being read. When an article is clicked on in Safari, it opens Firefox, which cannot read the format. The only way to restore the Safari functionality is to remove all instances of Firefox from the Mac. Reproducible: Always Steps to Reproduce: 1.Install Tiger (to get Safari 2.0) 2.Install stable or beta Firefox 3.Click on an article link in Safari RSS 4. Firefox opens even when Safari is default browser. Actual Results: Get error that Firefox cannot read the format of the feed. Expected Results: Nothing, Firefox should not have anything to do with Safari RSS articles!
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1 WFM with trunk,1.5b2 and 1.0.7. If i open safari and go to http://www.cnn.com/services/rss/ and open one of the feeds it doesn't open firefox it stays in safari and displays the feed. My Version of safari is Version 2.0.1 (412.5), and i'm running tiger with the 10.4.2 update.
This is embarrassing, I have been trying to work out this problem for weeks and after Paul's response I reinstalled Tiger and then Safari, thinking that the problem must be with Safari. Only then did I click RSS on Safari Prefs and discover that there is also a default RSS reader that can be set and I had set this to Firefox at some stage. Sorry, this is not a bug and the report should be removed. Mark
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.