webkitgtk[release-17.09]: 2.16.6 -> 2.18.2

[bendlas]

Motivation for this change

We need to keep stable secure.

Things done

Backported commits touching webkitgtk, including the update to 2.18.2, that I recently pushed to staging: ee0c629

• Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Fits CONTRIBUTING.md.

---

cc @fpletz

[fpletz]

Please use cherry-pick -x to add a reference to the picked commit.

[bendlas]

@fpletz done

[vcunat]

Well, about target branch being staging-17.09. This PR has conflicts wrt. release-17.09. Perhaps we should first merge it to staging-17.09 or something, so we solve conflicts in this PR already. (Otherwise it's not completely clear what we're merging.) Also note that we don't currently have any jobset for staging-17.09, but we can easily create it if 17.09 managers think so. (EDIT: I personally think it's OK now for 17.09 to merge mass rebuilds directly.)

BTW, libproxy still refers directly to webkitgtk216x, creating an evaluation error.

[vcunat]

In particular, note that on 17.09 we already have webkitgtk 2.18.1.

[bendlas]

OK, rebased the PR onto release-17.09

[bendlas]

couldn't find any references to webkitgtk216x in it

[vcunat]

Yes, that was just on the old base.

[vcunat]

Well, some pages don't render for me, but this PR doesn't seem to affect the problem, and it's the same on nixos-unstable. I tried epiphany and midori, e.g. google.com is shown just blank grey. Apparently the content is there, as shown by hovering over (invisible) links.

[vcunat]

Can't well test it (see my comment), but the change seems OK.