unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Using IceCat/geckodriver with Selenium (Python)
Date: Fri, 05 Nov 2021 14:48:46 -0400	[thread overview]
Message-ID: <87mtmi30c1.fsf@gmail.com> (raw)

Hello,

I'm sharing this bit of knowledge as it was not obvious at all.
Selenium is hard-coded to look for 'firefox' in a couple places, even in
the serialized settings it sends to the browser instance controlled by
geckodriver.

Here's the initialization that worked using Guix on the
core-updates-frozen-batched-changes branch (where 'geckodriver' was
recently added to IceCat):

--8<---------------cut here---------------start------------->8---
from selenium.webdriver import Firefox, FirefoxOptions
# Monkey patch the KEY string for IceCat.
FirefoxOptions.KEY = "moz:icecatOptions"
options = FirefoxOptions()
options.headless = False
options.binary = 'icecat'
options.set_capability('browserName', 'icecat')
self.driver = Firefox(options=options)# TODO:
--8<---------------cut here---------------end--------------->8---

The non-obvious was monkey patching the 'moz:icecatOptions' string of
the FirefoxOptions object, and having to set the 'browserName'
capability; otherwise a capability/invalid argument execption would be
raised.

If you use chromedriver (included with) our ungoogled-chromium instead,
it is more straightforward as there is nothing to rename/monkey patch:

--8<---------------cut here---------------start------------->8---
options = ChromeOptions()
options.headless = False
self.driver = Chrome(options=options)
--8<---------------cut here---------------end--------------->8---

I hope that helps someone else :-).

Maxim


             reply	other threads:[~2021-11-05 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 18:48 Maxim Cournoyer [this message]
2021-11-05 22:19 ` Using IceCat/geckodriver with Selenium (Python) Luis Felipe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mtmi30c1.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).