293440 - Modify safari's bookmarks directly

Status: VERIFIED WONTFIX

(Camino Graveyard :: Bookmarks, enhancement)

Description

[Ed Mellodew]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: 

Hi,

I wondered if it would possible to allow Camino to use safari bookmarks.  
Perhaps as an option in the system preferences.

This would allow Camino and Safari to always be in sync and optionally allow 
synchronisation of Safari/Camino bookmarks via .Mac.

I got thinking last night, and couldn't think why there is not a system wide 
bookmarks store, like keychain is for passwords.  I have 3 different web 
browsers on my Mac and all with various versions of bookmarks.  If you link 
that with my second Mac I now have six versions of bookmarks to maintain and 
it becomes a little un-manageable.

Ed

Reproducible: Always

Comment 1

[Mike Pinkerton (not reading bugmail)]

the problem here is that we have different fields and safari will not honor any
additions made to the plist that aren't in the set of keys it understands. the
user would lose a lot of functionality, and not really understand why. 

i'm gonna WONTFIX this. 

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

*** Bug 327288 has been marked as a duplicate of this bug. ***

Comment 4

[Didier Oswald]

(In reply to comment #1)
> the problem here is that we have different fields and safari will not honor any
> additions made to the plist that aren't in the set of keys it understands. the
> user would lose a lot of functionality, and not really understand why. 
> 
> i'm gonna WONTFIX this. 

Then Camino would just have to warn the user when he selects Safari as the bookmark source. Sacrifying this feature isn't that bad compared to all the benefits (iPod/iPhone/.Mac synchronisation).

I don't think that this is a WONTFIX, it's just a compromise ;-)

Comment 5

[Chris Lawson (gone)]

No.

As was stated in the other bug, you want .Mac synchronisation. Sharing a bookmarks file is not a viable substitute for that, especially when it means a fairly significant amount of dataloss (bookmarks shortcuts being probably the most important feature that Safari does not support).

Please read https://bugzilla.mozilla.org/page.cgi?id=etiquette.html before commenting further.

Comment 6

[Didier Oswald]

My intention wasn't to whine about the decision. I just wanted to say that some users would like iPod/iPhone sync for bookmarks (I don't really care about .Mac sync). Since I knew that iTunes was using Safari bookmarks, I just thought it was more relevent to post here directly rather than opening a new bug. But if you prefer, I can just create a new bug/enhancement to say that I would like my iPhone to sync its bookmarks with Camino too.


Anyway, I just wanted to point out that this issue could be resolved by using Safari bookmarks directly (not necessary with replacements, but for example by using both Safari AND Camino bookmarks - actually Camino would continue to use his own way to manage bookmars, ie with shortcuts - and always overwrite Safari bookmarks in order to be able to sync). Shortcuts would just be empty for new entries that were first added to Safari and then automatically imported in Camino. Of course that would also mean that we should have some sort of daemon that always auto-import new bookmarks in Camino when he detects that changes were made to Safari's Bookmarks.plist (and that is also true for the auto-export from Camino to Safari).

Comment 7

[Stuart Morgan]

If you want a persistent daemon that watches for changes to the bookmark files of several browsers and attempts to synchronize them, that would be something for a third-party to write, as it's clearly not within the scope of Camino itself. If you want a conduit for Camino to push bookmarks into Safari for iPhone directly, you would need to file a request with Apple, as there is no API for doing that. Neither is relevant to this bug.

This bug is specifically about stomping Safari's bookmarks and is--and will continue to be--WONTFIX, if for no other reason than the fact that without the ability to change Safari's code there is no way for us to prevent the very real possibility that bookmarks would be destroyed without users having any idea why. Neither attempting to change the scope of this bug nor arguing for this bug as filed to be fixed is appropriate.