Open Bug 1638207 Opened 4 years ago Updated 1 year ago

Firefox cannot sync proxy config in setting

Categories

(Firefox :: Sync, enhancement)

76 Branch
enhancement

Tracking

()

People

(Reporter: xuanlap93, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached image Screen Shot 2020-05-15 at 09.01.28.png (deleted) —

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.129 Safari/537.36

Steps to reproduce:

I create a firefox sync account
I access network setting after that i choose Manual proxy configuration
Enter HTTP Proxy, port...
I sync it on my account

Actual results:

when i login my account in other computer and sync firefox i cannot see my network setting

Expected results:

I need sync network setting

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Sync

Hi there, thanks for the report! You're right, it looks like we don't sync any of the network.proxy.* prefs that dialog sets.

In the past, we haven't been sure about the right way to support settings like this, because synced preferences are global. So (for example) if you're signed in to Sync on your home and work computers, and you set up a proxy on your work computer...oops, now your home computer will use the same proxy settings! In some cases, that might be what you want; in other cases—if you're only using a proxy at work, for example, and it's behind a VPN or requires you to be connected to the work network—it'll break your internet, with no easy way to figure out why.

If you'd like to sync these settings yourself, please follow these instructions to sync custom preferences. You'll need to add the following prefs to about:config, all of them set to true (sorry it's a hassle to do for this many prefs):

  • services.sync.prefs.sync.network.proxy.http
  • services.sync.prefs.sync.network.proxy.http_port
  • services.sync.prefs.sync.network.proxy.share_proxy_settings
  • services.sync.prefs.sync.network.proxy.ssl
  • services.sync.prefs.sync.network.proxy.backup.ssl
  • services.sync.prefs.sync.network.proxy.ssl_port
  • services.sync.prefs.sync.network.proxy.backup.ssl_port
  • services.sync.prefs.sync.network.proxy.ftp
  • services.sync.prefs.sync.network.proxy.backup.ftp
  • services.sync.prefs.sync.network.proxy.ftp_port
  • services.sync.prefs.sync.network.proxy.backup.ftp_port
  • services.sync.prefs.sync.network.proxy.socks
  • services.sync.prefs.sync.network.proxy.socks_port
  • services.sync.prefs.sync.network.proxy.socks_version
  • services.sync.prefs.sync.network.proxy.autoconfig_url
  • services.sync.prefs.sync.network.proxy.type
  • services.sync.prefs.sync.network.proxy.no_proxies_on
  • services.sync.prefs.sync.signon.autologin.proxy
  • services.sync.prefs.sync.network.proxy.socks_remote_dns
  • services.sync.prefs.sync.network.trr.mode
  • services.sync.prefs.sync.network.trr.uri
  • services.sync.prefs.sync.network.trr.resolvers
  • services.sync.prefs.sync.network.trr.custom_uri
Blocks: syncmore
Status: UNCONFIRMED → NEW
Type: defect → enhancement
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: