Closed Bug 358972 Opened 19 years ago Closed 18 years ago

microsummary bookmarks sorted by static title, not live title

Categories

(Firefox :: Bookmarks & History, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: myk, Assigned: rflint)

References

Details

Bookmarks which display a microsummary as their live title get sorted in the bookmarks manager by their static title, not their live title, when you click on the "Name" column to sort them by their "name". They should be sorted by the value that appears in that column, whether it is the static title or the live one.
Component: Bookmarks → Places
Depends on: 373500
OS: Linux → All
QA Contact: bookmarks → places
Hardware: PC → All
Fixed in bug 373500.
Assignee: nobody → ryan
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Myk, can you verify this or provide us with some test cases?
Yes, I can verify this. A testcase will be a bit complex to construct, but I should be able to create one of those as well.
Status: RESOLVED → VERIFIED
Myk, I was just looking for microsummary pages to test with. sorry for the confusion. But thanks for the verify.
(In reply to comment #4) > Myk, I was just looking for microsummary pages to test with. Ah, ok. If you want to do further testing, check out these sample sites: http://wiki.mozilla.org/Microsummaries/Sites
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h". In Thunderbird 3.0b, you do that as follows: Tools | Message Filters Make sure the correct account is selected. Click "New" Conditions: Body contains places-to-b-and-h Change the action to "Delete Message". Select "Manually Run" from the dropdown at the top. Click OK. Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter. Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in before you can comment on or make changes to this bug.