Closed Bug 106326 Opened 23 years ago Closed 23 years ago

Better handling of IE favorites

Categories

(SeaMonkey :: Bookmarks & History, enhancement, P2)

enhancement

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.9

People

(Reporter: trudelle, Assigned: bugs)

References

Details

Attachments

(1 file)

IE Favorites confuses users because their currently "read only" bookmarks as
opposed to "first class" bookmarks. Time estimate is 5 days.
marking p2, mozilla0.9.7, and blocking 75643
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9.7
related bugs: bug 56765 (wontfix), bug 68858 and bug 101174
What is this bug for?  The summary is very vague, and "IE Favorites confuses 
users because their currently 'read only' bookmarks as opposed to 'first class' 
bookmarks" could mean any of at least three things:

1. Users should be able to edit c:\windows\favorites\ from within Mozilla (bug 
56765).
2. Mozilla should actually import favorites instead of just displaying them 
(bug 59636).
3. IE favorites should look more read-only to avoid confusing users (bug 68858, 
bug 101174).

Is this a dup of one of those bugs, or is it something else that I didn't think 
of?
It is a tracking bug for scheduled Navigator tasks to better handle IE
favorites.  I think the planned approach will satisfy bug 59636, but I don't
think it needs to be resolved as a dup.

Ben's engineering plan is: "permanent import: 5 days (including UI) - import
dialog, importing .lnk  files and creating new bookmarks, maintain ability to
show live view."

Blocks: 102472
Severity: normal → enhancement
Pushing out to mozilla0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8
->ben
Assignee: pchen → ben
Status: ASSIGNED → NEW
what are the chances this will make 098?
-> .9.9
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.8 → mozilla0.9.9
I apologize for any rudeness, but this doesn't look like a tracking bug. The
component is currently "Bookmarks." In addition, there are no bugs that this bug
depends on. That said, this bug doesn't have a clear write-up. I admit that I am
frequently and woefully ignorant, but could someone give a description of what
bug this is a report of? What is the expected behavior? TIA.
Blocks: 120814
Andrew: This is for tracking feature work, not a defect. It is distinct from
normal defect bugs, or meta bugs or bugs which have dependencies.  You are right
about its still being too undefined.  It needs a clear write-up for expected
behavior.
Attached patch patchSplinter Review
hoboy. This patch includes extensive modifications to nsIBookmarksService to
tidy up the API, providing new helper methods for creating bookmarks and
folders. 

Also included are modifications which make the service do a one-off import of
system bookmarks on Mac and Windows into actual bookmarks and folders.
Various small nits:

o  createBookmarkEx() and createFolderEx() are vaguely named and beg for better
names

o  please break lines similiar to the following (there are several spots) onto
two separate lines:
      +  nsAutoString bookmarkName; bookmarkName.Assign(aName);

o  now that bug # 124322 has been fixed, bookmark types (nodes and folders but
NOT separators or IE types) are now synthesized instead of stored internally in
the graph, so the following can be removed:
      +  // Resource: type
      +  rv = mInner->Assert(bookmarkResource, kRDF_type,
              kNC_Bookmark, PR_TRUE);

o  to add with debugging (when setting breakpoints), please change from this style:
      +  if (NS_FAILED(rv)) return rv;
   to this style:
      +  if (NS_FAILED(rv))
      +      return rv;

o  Should expose the pref in the Prefs UI for Win & Mac users

o  HasArcIn() and HasArcOut() can be called a lot, and it looks like for Windows
it now calls IsContainer() for the systemroot. A small optimization you can make
it to have it call IsSeq() instead.

Fix the above, and r=rjc
Fixed. 
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Keywords: nsbeta1+
VERIFIED Fixed with 20020409 builds
Status: RESOLVED → VERIFIED
Since bug 59636 also blocks bug 120814 (meta), it's redundant (circular?) for
this bug to block both of them.  So, I'm removing bug 59636 from the blocker
list on this bug.

Since meta bug 102472 is specific to Netscape 6.x, it can "stay" blocked by this
FIXED bug.
No longer blocks: 59636
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: