Bug 200894 – [WebDriver][GTK] WebDriver css-selector fails on WebKitGTK+ 2.25.4 and Fedora 31 (rawhide)

• Component: WebDriver
• Status: RESOLVED DUPLICATE

[Carlos Alberto Lopez Perez]

The WebKitGTK WebDriver for 2.25.4 fails to execute a simply css-selector command on Fedora 31 (rawhide).

This issue is not reproducible with the WebDriver shipped by Debian experimental for the very same version of WebKitGTK (2.25.4).

I have inspected the patches shipped by both Debian and Fedora versions, as well as the different build options and at first sight I can't see nothing there to explain this different behaviour. Perhaps its related with some compiler bug.
The complete build logs, including build flags passed are here:
* Fedora: https://kojipkgs.fedoraproject.org/packages/webkit2gtk3/2.25.4/1.fc31/data/logs/x86_64/build.log
* Debian: https://buildd.debian.org/status/fetch.php?pkg=webkit2gtk&arch=amd64&ver=2.25.4-1&stamp=1565353274&raw=1

[Carlos Alberto Lopez Perez]

Created attachment 376704 [details]
simplified test case to reproduce the issue

I'm attaching a simplified test-case to reproduce the issue.
To test it do the following:
1) On a terminal open WebKitWebDriver to listen on 127.0.0.1:444
WebKitWebDriver --host=127.0.0.1 --port=4444
2) On another terminal run the attached script. Pass "epiphany" to execute epiphany from the webdriver or pass the path to the minibrowser to execute with the MB.

If it works as expected it should print something like:
{"value":null}{"value":[{"element-6066-11e4-a52e-4f735466cecf":"node-31A8F3A7-8142-4F75-B80F-538E5208ED28"}]}

But on Fedora it always prints:
{"value":null}{"value":{"error":"javascript error","message":"Unexpected string literal '/'. Expected ')' to end a compound expression.","stacktrace":""}}

[Carlos Alberto Lopez Perez]

The issue is also reproducible on Fedora 30 with webkit2gtk3-2.24.3-1.fc30

[Carlos Alberto Lopez Perez]

I have hunted down the issue to be caused when WebKitGTK+ is built with python3 instead of python2.

Passing "-DPYTHON_EXECUTABLE=/usr/bin/python3" to the build or building on a system that doesn't have python2 (CMake will pick python3 if it can't find python2) causes this problem.

The problem is very likely caused by some of the python scripts that are run as part of the build process that generate code.

[Carlos Alberto Lopez Perez]

*** This bug has been marked as a duplicate of bug 194367 ***