当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

command line changed in version 67?

more options

I have a number of scripts for Windows that I use to open multiple searches in multiple Firefox tabs. I don't use bookmarks because I have to preprocess the search argument to put it into the correct format for each of the individual search URLs.

Each line in the script launches Firefox from the command line with a different search URL. Up until now, each invocation opened a new tab in the currently active Firefox window.

All of a sudden it no longer works. The first Firefox invocation opens a tab in a new window. The new window has no title bar or bookmark toolbar (see attached image). The script then hangs until I kill the new window and then wait 10 seconds; then the next URL opens in another new window.

What changed? Is there any way for me to add tabs to an active Firefox window from the Windows command line?

I have a number of scripts for Windows that I use to open multiple searches in multiple Firefox tabs. I don't use bookmarks because I have to preprocess the search argument to put it into the correct format for each of the individual search URLs. Each line in the script launches Firefox from the command line with a different search URL. Up until now, each invocation opened a new tab in the currently active Firefox window. All of a sudden it no longer works. The first Firefox invocation opens a tab in a new window. The new window has no title bar or bookmark toolbar (see attached image). The script then hangs until I kill the new window and then wait 10 seconds; then the next URL opens in another new window. What changed? Is there any way for me to add tabs to an active Firefox window from the Windows command line?
添付されたスクリーンショット

選ばれた解決策

Hi cbenenax, Firefox 67 has changed how external links open when you have multiple profiles. It seems Firefox will always use the default profile, even if you started Firefox and it currently is running in a different, non-default profile.

Could you take a look on the Profile Manager page:

Inside Firefox, type or paste about:profiles in the address bar and press Enter/Return to load it.

Firefox may list multiple profiles here, each with information about its folder locations (you can ignore that for the moment). The currently running profile should have:

This is the profile in use and it cannot be deleted.

If that profile has a button below its table to Set as default profile try clicking that button. If it doesn't have that button, hmm, I'll need to come up with Plan B.

この回答をすべて読む 👍 0

すべての返信 (4)

more options

選ばれた解決策

Hi cbenenax, Firefox 67 has changed how external links open when you have multiple profiles. It seems Firefox will always use the default profile, even if you started Firefox and it currently is running in a different, non-default profile.

Could you take a look on the Profile Manager page:

Inside Firefox, type or paste about:profiles in the address bar and press Enter/Return to load it.

Firefox may list multiple profiles here, each with information about its folder locations (you can ignore that for the moment). The currently running profile should have:

This is the profile in use and it cannot be deleted.

If that profile has a button below its table to Set as default profile try clicking that button. If it doesn't have that button, hmm, I'll need to come up with Plan B.

more options

Doesn't have Set as default profile button. See image.

more options

Oh, wait. The window that was open before I launched the script did not have the button, but the new window that opened did have it.

I pressed the button, closed the new window, and relaunched the script. It then worked as expected. Thanks.

more options

Hi cbenenax, thank you for exploring that and reporting back.

We're still trying to get a better understanding of the step being missed during some updates so the developers can try to prevent the problem from occurring, but it's taking a while to fill in the picture.