Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

MacOS keeps opening the old Pixelmator not Pixelmator Pro

  • 2 réponses
  • 0 a ce problème
  • 8 vues
  • Dernière réponse par Lanark

more options

When I download an image in Firefox and open it from the downloads folder it will always open in Pixelmator not Pixelmator Pro.

If I double click on an image file elsewhere they correctly open in Pro, but in Finder, the icons are for Pixelmator not Pixelmator Pro. This can be hidden if I turn on finder icon previews, but selecting Get Info always has the Pixelmator icon not the Pixelmator Pro one.

Im not sure if this is a macOS problem, a firefox issue or a Pixelmator bug but it seems to be related to the way the files are registered.

Things I have tried:

Changing file associations in firefox. Rebooting Changing the open-with properties in finder: Open all with Pixelmator Pro Reset the Local & User domains with lsregister lsregister -kill -r -domain local -domain user -domain system -v

When I download an image in Firefox and open it from the downloads folder it will always open in Pixelmator not Pixelmator Pro. If I double click on an image file elsewhere they correctly open in Pro, but in Finder, the icons are for Pixelmator not Pixelmator Pro. This can be hidden if I turn on finder icon previews, but selecting Get Info always has the Pixelmator icon not the Pixelmator Pro one. Im not sure if this is a macOS problem, a firefox issue or a Pixelmator bug but it seems to be related to the way the files are registered. Things I have tried: Changing file associations in firefox. Rebooting Changing the open-with properties in finder: Open all with Pixelmator Pro Reset the Local & User domains with lsregister lsregister -kill -r -domain local -domain user -domain system -v

Solution choisie

OK I think I found a fix.

I created and saved a .jpg file in Pixelmator Pro.

Open the file in Firefox using File, Open.

Save the file to the downloads folder.

Open the file by clicking on it in the downloads list - it correctly opens in Pixelmator Pro.

Now returning to the original website and saving another .jpg image, it correctly opens from the downloads list in Pixelmator Pro.

Im guessing Firefox just remembers the last graphics editor used and sticks to that even when the macOS file associations point to something different. Opening a file directly on the local file system should mean the files extended attributes take over and force a different choice of Editor application.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (2)

more options

The file association works fine when opening files in the mac finder.

It is only opening from the Firefox downloads list that it goes wrong.

Also if I download the same file in Google chrome and open it from the chrome downloads list that is also fine, so I think the problem must be in Firefox.

more options

Solution choisie

OK I think I found a fix.

I created and saved a .jpg file in Pixelmator Pro.

Open the file in Firefox using File, Open.

Save the file to the downloads folder.

Open the file by clicking on it in the downloads list - it correctly opens in Pixelmator Pro.

Now returning to the original website and saving another .jpg image, it correctly opens from the downloads list in Pixelmator Pro.

Im guessing Firefox just remembers the last graphics editor used and sticks to that even when the macOS file associations point to something different. Opening a file directly on the local file system should mean the files extended attributes take over and force a different choice of Editor application.

Modifié le par Lanark