Open Bug 409969 Opened 17 years ago Updated 1 month ago

Sync custom dictionaries


(Firefox :: Sync, enhancement, P5)






(Reporter: sdwilsh, Unassigned)


(Blocks 1 open bug)


(Keywords: parity-chrome, Whiteboard: [sync-engine-addition])

People add custom words to their dictionaries all the time.  It'd be awesome if these were synced across browsers using weave.
I agree!  That would be very nice.  I'd like to see a lot of the profile move up into the cloud, really.

I'm not sure where dictionaries fall wrt cookies, passwords, prefs, etc.
Severity: normal → enhancement
The other issue of course is what do you do on OS X since we use the system dictionary...
If the system dictionary on OS X differentiates between built-in and custom words, then we could simply sync the custom words to and from that dictionary just as we do for the non-system dictionaries on other OSes.
Cool idea!
How about syncing settings for addons too?
It'd be great if I could sync my noscript & adblock settings between machines.
Those should be new bugs - please do not hijack this one (also darn near impossible unless they store things in prefs).
(In reply to comment #4)
> How about syncing settings for addons too?

I filed the following:
Bug 428373 - Store Extension specific data files
Bug 428370 - Store all Preferences in prefs.js
Targeting for 0.3
Target Milestone: 0.1 → 0.3
Priority: -- → P2
-> future
OS: Mac OS X → All
Hardware: PC → All
Target Milestone: 0.3 → Future
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
Component: General → Sync
QA Contact: general → sync
Blocks: 530399
Would this include whole dictionaries (eg. the Australian English dictionary) or just custom words?
ideally both, although not the same way.

if i install es-ES into my desktop computer, it's reasonable to assume that I want to be able to write in es-ES *anywhere*. Thus the request to install the same dictionary (component/extension/whatever) should apply to other synced instances. However as noted in comment 5 extensions/whole dictionaries should be out of scope.

however, as a priority, it's probably more important to sync custom dictionaries (and comment 0 clearly indicates _custom_ - adjusting summary).
Summary: Weave should sync dictionaries → Weave should sync custom dictionaries
Priority: P2 → P4
Whiteboard: [sync-engine-addition]
Summary: Weave should sync custom dictionaries → Sync custom dictionaries
Whiteboard: [sync-engine-addition] → [sync-engine-addition][parity-chrome]
FYI, Chrome just released the stable v26 which includes this feature:
Flags: firefox-backlog?
Flags: firefox-backlog? → firefox-backlog+
Would be really nice to have this, adding words to custom dictionary over and over again on different PCs is of the biggest day-to-day annoyances of Firefox.
Blocks: syncmore
Just out of curiosity how hard would it be to code this?
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [sync-engine-addition][parity-chrome] → [sync-engine-addition]
Component: Firefox Sync: Backend → Sync
Priority: P4 → --
Product: Cloud Services → Firefox
Priority: -- → P3

any estimation when you plan to implement this feature? :)
Syncing custom dictionary.

thank you in advance.

PS: you are doing great job.

Priority: P3 → P5

I'm still surprised that this, relatively simple?, feature is not implemented yet - i follow this thread without commenting since a decade and always believed that this must be such a clear one (and similar to bookmarks) that i will get done.

I use four installations of FF (1 work and 2 personal PCs, one mobile) and am constantly hitting the same words again and again.

Seeing as the services.sync.prefs.sync.spellchecker.dictionary config exists and is set to true by default when syncing, hasn't this bug been resolved? I don't know when the syncing was implemented, but it seems to have been implemented.

Flags: needinfo?(markh)

I believe this just syncs the name of the preferred/default dictionary, not the dictionary itself.

Flags: needinfo?(markh)

I've been doing the syncing of my custom dictionary file by hand/scripted among my various systems over the years.

Following this 15 year old bug report I often wonder - is this too simple to be included as browser functionality since it's just a small text file in question? Or, are the majority of users big fans of red squigglies?

Conversely I've been following another 14 year old gem of a bug which at least appears difficult to implement due to early db design decisions.

Love FF so much and have evangelized it since Phoenix. These decades old bugs still... bug me!

So who can take the decision to implement it and get it done. As a user I do hate the situation.

Flags: needinfo?(sdwilsh)

This is not on the sync team's roadmap as we are busy with higher priority work.

Flags: needinfo?(sdwilsh)
Severity: normal → S3
Duplicate of this bug: 1874601
You need to log in before you can comment on or make changes to this bug.