Just wondering if this is a bug that's likely to get fixed anytime soon. Or is there something inherintely blocking it from working like something that would have to change in windows or firefox to make it work. I'm only asking because I was going to start work on a work around, but that will likely be a bunch of work so I thought I'd check first.
Just wanted to let you know that we're still working on this bug (1609175). I don't believe it will be fixed in time for the next runtime update but I'll update our internal bug with this thread url.
Thanks for the update I appreciate the info. For now I wrote a work around
using NativeProcess in AIR2. If we're on a Mac we just use navigateToURL,
but if we're on a windows machine we locate firefox.exe and run it with the
-new-tab argument. Seems to work for now but it will be better to just use
navigateToURL for both