So setting the LAUNCHPAD_BROWSERS environment variable before running wct 
seems to fix the problem. I guess this means the browser list in 
wct.conf.json (or passed in via -l) is being ignored by wct ?

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/b010591c-5125-43dc-baea-d06aff514ceb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to