More strange, I can pin the active instance. This pin *does* combine with a running instance of firefox.ĭirectly dragging and pinning the "Firefox A" shortcut does succeed in pinning the shortcut itself, but does not combine with the running instance itself O.o. Pinning my active firefox run from a shortcut called "Firefox A" doesn't retain the run settings from "Firefox A" in this case -P "Firefox1" it instead runs the default profile. (Even if it may have been *implemented* wrong, it worked right.) It worked, as far as I could tell, perfectly waaay back in 3.5 and I think up until 3.6. No offence? But the pinning behavior in 10 is ~bad~. Happens even running a single instance, just is more irritating if running multiple. The pinned icon should have expanded into a window-taskbar item.
/dev/null' title='wine '/users/michael byrne/.wine/drive_c/program files/houdini 6 chess/houdini 6.exe' 2>/dev/null' />left-click said pinned item, watch the wrongnessįirefox starts, but creates a new taskbar item instead of replacing the pinned item, leaving a pinned item laying around. Make shortcut named anything other than Mozilla Firefox that starts firefoxģ. Worked fine in Firefox 3.5(Possibly newer pre4.0, I forget exactly what I was updated to but I've been doing this since 3.0), a shortcut named "Mozilla Firefox 1" would stay bonded to the firefox instance it started if pinned.ġ. (2 of which run -no-remote -p profile1( and profile2 and profile3) but irritating even with a single instance. Try pinning a shortcut named "Firefox 1" and then use it, firefox will partially seperate itself from the icon leaving the icon in the W7 taskbar AND adding a window of firefox.Įspecially undesirable if like me, you use 3 instances of firefox.