User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 When right-click on an image, there is the option 'block images from <site>' Weave should synchronize these preferences. Reproducible: Always

Ping! With click-to-play becoming more widespread all the time, this is becoming more important.

(In reply to Dirkjan Ochtman (:djc) from comment #2) > Ping! With click-to-play becoming more widespread all the time, this is > becoming more important. It is very unlikely that the services-integration team will ever address this, or any other outstanding feature request for Sync.

Really would like to see this worked on... it's features like Sync that allow FF to compete effectively with Chrome.

This will probably be on the eventual list for the ongoing rework of Sync. But I wouldn't hold my breath -- there's a lot more important stuff to be done.

(In reply to Richard Newman [:rnewman] from comment #6) > This will probably be on the eventual list for the ongoing rework of Sync. > But I wouldn't hold my breath -- there's a lot more important stuff to be > done. Hello Richard, It's been 1 year and a half since your reply, so hopefully a whole "lot of more important stuff" has been done - and we can certaily see it in our everyday browsing experience. Still, lack of support of "permissions.sqlite" in Firefox Sync is *immensely* missed. To put it like in bug #44360 which initiated this request in 2008, syncing cookies settings without syncing specific per site user defined authorizations/denials is useless. In this very ticket Dirkjan & Eli expressed how important this is, and I could not agree more with them. Having to handle manually ""syncing"" of permissions.sqlite is a real PITA. What I'm most concerned about is one of your latest comment: "It is very unlikely that the services-integration team will ever address this, or any other outstanding feature request for Sync." => Does this mean Firefox Sync is on the verge of being abandoned - or slowly put to rest? => Will handling of permissions.sqlite in Firefox Sync be ever be addressed or is it rejected? => If included in roadmap, what would be ETA? If definitely rejected, could you clearly say so? My thanks.

(In reply to OptimusIV from comment #7) > => Does this mean Firefox Sync is on the verge of being abandoned - or > slowly put to rest? I doubt it. But it doesn't have a dedicated team to drive improvements. > => Will handling of permissions.sqlite in Firefox Sync be ever be addressed > or is it rejected? It's a difficult piece of work that requires some finesse (as is almost everything involving Sync), and there's no developer who's championing the work. That means there are two ways it could happen: * Someone could nominate it for the funnel, and the desktop team could decide to work on it as part of their routine sprints. Doing so means essentially competing against all other important and overdue desktop work. * A higher-level product drive on Sync could occur, and a bunch of bugs like these could be addressed. > => If included in roadmap, what would be ETA? If definitely rejected, could > you clearly say so? It is neither in a roadmap nor rejected, which is why the bug is marked as NEW. I don't really see it happening any time soon unless someone in leadership decides to spend a bunch of resources on making Sync better as a whole. That said, if a competent developer decided to work on it, I would certainly make an effort to review the code and offer advice.

(In reply to Richard Newman [:rnewman] from comment #8) > (In reply to OptimusIV from comment #7) > > > => Does this mean Firefox Sync is on the verge of being abandoned - or > > slowly put to rest? > > I doubt it. But it doesn't have a dedicated team to drive improvements. > > > > => Will handling of permissions.sqlite in Firefox Sync be ever be addressed > > or is it rejected? > > It's a difficult piece of work that requires some finesse (as is almost > everything involving Sync), and there's no developer who's championing the > work. That means there are two ways it could happen: > > * Someone could nominate it for the funnel, and the desktop team could > decide to work on it as part of their routine sprints. Doing so means > essentially competing against all other important and overdue desktop work. > > * A higher-level product drive on Sync could occur, and a bunch of bugs like > these could be addressed. > > > > => If included in roadmap, what would be ETA? If definitely rejected, could > > you clearly say so? > > It is neither in a roadmap nor rejected, which is why the bug is marked as > NEW. I don't really see it happening any time soon unless someone in > leadership decides to spend a bunch of resources on making Sync better as a > whole. > > That said, if a competent developer decided to work on it, I would certainly > make an effort to review the code and offer advice. Hello Richard, Thank you for these information & explanations. I'll patiently wait for that competent developer to show up. Or any one of the three other possibilities you mentioned to happen. Best.