Bug 750942 - Cannot change dynamic bookmark - jumps back after second reload
Summary: Cannot change dynamic bookmark - jumps back after second reload
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 21:47 UTC by Thomas Meyer
Modified: 2012-05-04 08:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-04 08:56:42 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Meyer 2011-11-02 21:47:57 UTC 
Description of problem:

I have a dynamic bookmark with these settings:


Name: linux-3.0.git
Feed address: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=rss;h=refs/heads/linux-3.0.y
Web address: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=log;h=refs/heads/linux-3.0.y
Description:


When I open the properties of the dynamic bookmark "linux-3.0.git" and replace all occurrences of "3.0" with "3.1" and save and reload the dynamic bookmark, it shows me the correct new feed info.

But after a second reload the feed address jumps back to "http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=rss;h=refs/heads/linux-3.0.y" address and shows me the old feed info again!
Comment 1 Martin Stransky 2012-05-04 08:50:14 UTC 
I tried to reproduce it but it failed only first time, when I tried second time the feed address was saved and updated properly. Can you please try to reproduce with latest Firefox (12)?
Comment 2 Martin Stransky 2012-05-04 08:56:42 UTC 
Ah, I see. It looks like the bookmark address is not supposed to be editable, it's disabled in the new firefox version. So you have to create a new feed for the 3.1 feed and remove the old one.
Note You need to log in before you can comment on or make changes to this bug.