Closed
Bug 388860
Opened 17 years ago
Closed 17 years ago
New folder button on Add Bookmark panel does nothing
Categories
(Firefox :: Bookmarks & History, defect)
Firefox
Bookmarks & History
Tracking
()
RESOLVED
FIXED
Firefox 3 alpha7
People
(Reporter: cmtalbert, Assigned: moco)
References
Details
(Keywords: regression)
Attachments
(1 file, 2 obsolete files)
4.34 KB,
patch
|
asaf
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a7pre) Gecko/2007071904 Minefield/3.0a7pre Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a7pre) Gecko/2007071904 Minefield/3.0a7pre Clicking the "New Folder" button on the "Add Bookmarks" panel does nothing. I have confirmed this bug also on Windows XP: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071905 Minefield/3.0a7pre The odd thing about this is that no exception is thrown in the Error Console, or even in the console spew on a debug build. Reproducible: Always Steps to Reproduce: 1. Go to a page in Minefield 2. Click Bookmarks -> Bookmark This Page 3. Click the drop down arrow 4. Click on "New Folder" Actual Results: No folder is created, regardless of where in the current tree you are selected. Expected Results: Folder should be created == Regression Range == Works: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071008 Minefield/3.0a7pre Breaks: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7pre) Gecko/2007071105 Minefield/3.0a7pre Bonsai query for this range (on the entire tree) http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=mozilla%2F&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-07-10+00%3A00%3A00&maxdate=2007-07-11+13%3A00%3A00&cvsroot=%2Fcvsroot
Comment 1•17 years ago
|
||
Broken also on Windows: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a7pre) Gecko/2007071905 Minefield/3.0a7pre Firefox/3.0 ID:2007071905
Assignee | ||
Comment 2•17 years ago
|
||
I think this is something I broke, with my fix for bug #385990
Assignee: nobody → sspitzer
Depends on: 385990
Keywords: regression
Target Milestone: --- → Firefox 3 M8
Assignee | ||
Comment 3•17 years ago
|
||
avoid my history query optimization by specifying queryType=1 (QUERY_TYPE_BOOKMARKS)
Attachment #273053 -
Flags: review?(dietrich)
Assignee | ||
Updated•17 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [SWAG: patch in hand awaiting review]
Target Milestone: Firefox 3 M8 → Firefox 3 M7
Comment 4•17 years ago
|
||
Comment on attachment 273053 [details] [diff] [review] fix hrm, we should probably recommend that queryType always be used for bookmarks queries now.
Attachment #273053 -
Flags: review?(dietrich) → review+
Assignee | ||
Comment 5•17 years ago
|
||
> hrm, we should probably recommend that queryType always be used for bookmarks
> queries now.
I've added an assert so that we'll catch this problem next time, and it won't be silent.
I'll attach that patch.
Assignee | ||
Comment 6•17 years ago
|
||
carrying over dietrich review
Attachment #273053 -
Attachment is obsolete: true
Attachment #273078 -
Flags: review+
Assignee | ||
Comment 7•17 years ago
|
||
fixed. Checking in content/bookmarkProperties.js; /cvsroot/mozilla/browser/components/places/content/bookmarkProperties.js,v <-- bookmarkProperties.js new revision: 1.56; previous revision: 1.55 done Checking in content/bookmarkProperties.xul; /cvsroot/mozilla/browser/components/places/content/bookmarkProperties.xul,v <-- bookmarkProperties.xul new revision: 1.27; previous revision: 1.26 done Checking in content/tree.xml; /cvsroot/mozilla/browser/components/places/content/tree.xml,v <-- tree.xml new revision: 1.79; previous revision: 1.78 done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•17 years ago
|
||
re-opening, I backed out because the tree was closed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•17 years ago
|
Status: REOPENED → ASSIGNED
Comment 9•17 years ago
|
||
I don't think this is right, queryType should be ignored for simple folder queries. I would rather make getinsertionpoint check queryType only if the root is a query node (nodeIsQuery).
Updated•17 years ago
|
Attachment #273078 -
Flags: review-
Assignee | ||
Comment 10•17 years ago
|
||
Attachment #273078 -
Attachment is obsolete: true
Attachment #273172 -
Flags: review?(mano)
Comment 11•17 years ago
|
||
Comment on attachment 273172 [details] [diff] [review] patch, per mano (plus some cleanup) r=mano
Attachment #273172 -
Flags: review?(mano) → review+
Assignee | ||
Comment 12•17 years ago
|
||
fixed. Checking in content/bookmarkProperties.js; /cvsroot/mozilla/browser/components/places/content/bookmarkProperties.js,v <-- bookmarkProperties.js new revision: 1.58; previous revision: 1.57 done Checking in content/tree.xml; /cvsroot/mozilla/browser/components/places/content/tree.xml,v <-- tree.xml new revision: 1.81; previous revision: 1.80 done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•17 years ago
|
Flags: in-litmus?
Flags: blocking-firefox3?
Whiteboard: [SWAG: patch in hand awaiting review]
Updated•17 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Comment 13•17 years ago
|
||
Litmus Triage Team: cc'ing al and tracy for the in-litmus flag
Comment 14•15 years ago
|
||
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.
Description
•