Launching multiple urls from tasker

[Katherine Davis]

Hey everyone,

I'm trying to create a task that will read a bunch of urls (1-5) from a file and open them in different tabs in my default browser. I've set things up like this:

%url_number is the number of URLs in the file +1 to account for eof results
The urls each have their own individual line in the file

For
%loop_number, 1:%url_number
  Read line
    (from file) to %url
  Browse URL
     %url
     IF %url~!eof
End For

This only opens the last URL in the file, but if I tell tasker to flash %url as part of the loop, all of the URLs are flashed, so I know that it is looking them all up properly. I think it's a constraint with Browse URL.

I've also tried setting the line read to %loop_number; that had the exact same result.

Anyone have any ideas around this?

Thanks!

[Bob Hansen]

You can open new windows in a browser using a Send Intent action like this:

        A1: Send Intent [ Action:android.intent.action.VIEW Cat:None Mime Type: Data:http://www.google.com Extra:new_window:true Extra: Package:mobi.mgeek.TunnyBrowser Class: Target:Activity ]

You will need to change the Data: to your url.

The Package: list is for the Dolphin browser. You can try leaving it blank and if that doesn't work replace it with the package name of your browser. 

You may need to add a delay between sending each new url - I didn't try it.

Hope this helps.

[Katherine Davis]

I tried that, and it does open the correct browser, but again it doesn't use a new tab. I'm using Naked Browser, BTW-I don't know if that makes a difference. I added a one second wait time and was able to confirm that all of the urls are loading, just in the same tab.

[Bob Hansen]

It appears that the Naked Browser doesn't support the new window intent. Care to try the Dolphin browser? As far as I am concerned, it is the best android browser.

[Katherine Davis]

 Interestingly enough, I tried Dolphin (I've been thinking about switching for a while, but I love the full screen thing naked browser has going on, so I was putting it off) and it had the same issue. So then I tried the native browser, and it worked!

Thanks for the help.