Watir has a shortcut for headless right now: Watir::Browser.new :chrome, headless: true
All it is doing is the first of the two switches you mentioned, though. As for what is currently supported, we run all of our specs with headless turned on (on Linux), and you can see by the guards we've put in place in the _spec files what isn't supported yet: https://github.com/watir/watir/search?q=headless Right now it is mostly alerts, multiple window handling and event firing. Most other things should work just fine. It's still a new feature, though, so expect it to improve. Titus On Tuesday, September 12, 2017 at 8:32:03 AM UTC-7, juan Barbera wrote: > > Hi all > > Currently i m using a ruby -watir framework with docker , i m trying to > test the new native headless of chrome without xvfb , but seems that there > are still some issues, as example with native headless watir is unable to > find some elements that works on chrome with xvfb , has anyone achieve a > succesfull test with chrome headless native. > > My system : > > Ubuntu 16.04 > Chrome 61 > Chromedriver 2.31 > > browser = Watir::Browser.new :chrome, > switches: %w[--headless > --disable-gpu --no-sandbox > --disable-prompt-on-repost > --windows-size=3200x1800] > > -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
