about summary refs log tree commit diff
path: root/pkgs/applications/networking/browsers
AgeCommit message (Collapse)AuthorFilesLines
2022-12-04Merge pull request #204362 from mweinelt/weird-animal-cleanupsMartin Weinelt1-5/+3
2022-12-04buildMozillaMach: Cleanup obsolete version gatesMartin Weinelt1-5/+3
2022-12-04Merge pull request #204365 from primeos/ungoogled-chromiumMichael Weiss1-4/+4
ungoogled-chromium: 108.0.5359.72 -> 108.0.5359.95
2022-12-04Merge pull request #204364 from primeos/chromiumMichael Weiss1-6/+6
chromium: 108.0.5359.71 -> 108.0.5359.94
2022-12-04chromium: 108.0.5359.71 -> 108.0.5359.94Michael Weiss1-6/+6
https://chromereleases.googleblog.com/2022/12/stable-channel-update-for-desktop.html This update includes 1 security fix. Google is aware that an exploit for CVE-2022-4262 exists in the wild. CVEs: CVE-2022-4262
2022-12-04ungoogled-chromium: 108.0.5359.72 -> 108.0.5359.95Michael Weiss1-4/+4
2022-12-03Merge pull request #202629 from ↵Martin Weinelt1-21/+20
atorres1985-contrib/firefox-use-enablefeature-directly
2022-12-03palemoon: 31.4.0 -> 31.4.1.1OPNA26081-2/+2
2022-12-03Merge pull request #204129 from buckley310/2022-12-02-braveMartin Weinelt1-2/+2
2022-12-02brave: 1.43.89 -> 1.46.133Sean Buckley1-2/+2
https://community.brave.com/t/release-channel-1-46-133/449943
2022-12-02ungoogled-chromium: 107.0.5304.122 -> 108.0.5359.72Michael Weiss2-12/+8
2022-12-02Merge pull request #203996 from primeos/chromiumDevMichael Weiss1-6/+6
chromiumDev: 109.0.5414.10 -> 110.0.5449.0
2022-12-01chromiumDev: 109.0.5414.10 -> 110.0.5449.0Michael Weiss1-6/+6
2022-12-01chromiumBeta: 108.0.5359.71 -> 109.0.5414.25Michael Weiss1-6/+6
2022-11-30chromium: 107.0.5304.121 -> 108.0.5359.71Michael Weiss1-10/+10
https://chromereleases.googleblog.com/2022/11/stable-channel-update-for-desktop_29.html This update includes 28 security fixes. CVEs: CVE-2022-4174 CVE-2022-4175 CVE-2022-4176 CVE-2022-4177 CVE-2022-4178 CVE-2022-4179 CVE-2022-4180 CVE-2022-4181 CVE-2022-4182 CVE-2022-4183 CVE-2022-4184 CVE-2022-4185 CVE-2022-4186 CVE-2022-4187 CVE-2022-4188 CVE-2022-4189 CVE-2022-4190 CVE-2022-4191 CVE-2022-4192 CVE-2022-4193 CVE-2022-4194 CVE-2022-4195
2022-11-30chromiumBeta: 108.0.5359.48 -> 108.0.5359.71 (#203681)Michael Weiss1-3/+3
* chromiumBeta: 108.0.5359.48 -> 108.0.5359.62 * chromiumBeta: 108.0.5359.62 -> 108.0.5359.71
2022-11-30buildMozillaMach: use enableFeature instead of recreating itAndersonTorres1-21/+20
2022-11-29Merge pull request #202555 from 06kellyjac/braveMario Rodas1-1/+1
brave: fix commandLineArgs option also requiring vulkanSupport
2022-11-29Merge pull request #203532 from wegank/ladybird-fixRobert Scott1-6/+23
ladybird: fix build
2022-11-29firefox-bin-unwrapped: 107.0 -> 107.0.1Martin Weinelt1-393/+393
https://www.mozilla.org/en-US/firefox/107.0.1/releasenotes/
2022-11-29firefox-unwrapped: 107.0 -> 107.0.1Martin Weinelt1-2/+2
https://www.mozilla.org/en-US/firefox/107.0.1/releasenotes/
2022-11-29ladybird: fix buildWeijia Wang1-6/+23
2022-11-28chromiumBeta: Fix the buildMichael Weiss1-0/+1
We do already set `system_wayland_scanner_path` to `"${wayland}/bin/wayland-scanner"` but apparently wayland-scanner wasn't required (anymore?) as wayland-scanner is only in the `bin` output (I have a few ideas what could've changed but didn't bother to check as it isn't worth the time as long as it works now). This fixes the following build error: ``` ninja: error: '../../../../../../../../nix/store/l3y9k2x7cqzcjj9s18z7la9xqsjq6r52-wayland-1.21.0/bin/wayland-scanner', needed by 'gen/components/exo/wayland/protocol/aura-shell-protocol.c', missing and no known rule to make it ```
2022-11-28Merge pull request #203119 from OPNA2608/update/palemoonAnderson Torres2-3/+3
palemoon: 31.3.1 -> 31.4.0
2022-11-28Merge pull request #202919 from SuperSandro2000/polypaneSandro1-1/+1
2022-11-27chromiumBeta: Fix the configuration phaseMichael Weiss1-0/+7
Upstream switched use_system_libwayland to false [0] and system_wayland_scanner_path will now only be declared if use_system_wayland_scanner is set to true (it defaults to use_system_libwayland) [1]. In Nixpkgs, we usually try to set use_system_* to true (i.e., we favor system libraries over bundled/vendored ones) but in the case of Chromium this can become difficult to maintain so we might eventually drop `use_system_libwayland = true` again (IIRC this only caused one incompatibility in the past though: b6b51374fc7; and f9d9864cb62 will become relevant again when we build with the bundled libwayland). [0]: https://source.chromium.org/chromium/chromium/src/+/b33bdfe2654df61dee900e7b85cc3fcaea6b65a3 [1]: https://source.chromium.org/chromium/chromium/src/+/272220cefa2cff8cf9273a02155454650e79e024
2022-11-26lagrange: 1.13.8 → 1.14.1Nikolay Korotkiy1-6/+6
2022-11-26palemoon: 31.3.1 -> 31.4.0OPNA26082-3/+3
2022-11-26Merge pull request #202869 from michaeladler/ungoogledMichael Weiss1-5/+5
ungoogled-chromium: 107.0.5304.110 -> 107.0.5304.122
2022-11-25polypane: fix source hashSandro Jäckel1-1/+1
2022-11-25ungoogled-chromium: 107.0.5304.110 -> 107.0.5304.122Michael Adler1-5/+5
2022-11-24chromium: 107.0.5304.110 -> 107.0.5304.121Michael Weiss1-3/+3
https://chromereleases.googleblog.com/2022/11/stable-channel-update-for-desktop_24.html This update includes 1 security fix. Google is aware that an exploit for CVE-2022-4135 exists in the wild. CVEs: CVE-2022-4135
2022-11-24Merge pull request #202589 from panicgh/tbbSandro1-3/+3
2022-11-23tor-browser-bundle-bin: 11.5.7 -> 11.5.8Nicolas Benes1-3/+3
https://blog.torproject.org/new-release-tor-browser-1158/
2022-11-23brave: fix commandLineArgs option also requiring vulkanSupport06kellyjac1-1/+1
2022-11-21chromiumDev: 109.0.5410.0 -> 109.0.5414.10Michael Weiss1-6/+6
2022-11-20Merge pull request #201705 from helsinki-systems/unalias-libheimdailajs1241-2/+2
libheimdal: turn into proper alias
2022-11-20Merge pull request #201775 from KiruyaMomochi/masterBobby Rong1-6/+6
microsoft-edge: 105.0.1343.42 -> 107.0.1418.52
2022-11-19luakit: 2.3 -> 2.3.1Daniel Nagy1-2/+2
2022-11-18microsoft-edge: 105.0.1343.42 -> 107.0.1418.52百地 希留耶1-6/+6
2022-11-18Merge #201359: firefox, thunderbird, librewolf: Enable wayland support by ↵Vladimír Čunát1-3/+2
default
2022-11-18libheimdal: turn into proper aliasajs1241-2/+2
2022-11-17Merge #201665: librewolf: drop upstreamed patchVladimír Čunát1-8/+2
2022-11-17librewolf: drop upstreamed patchVladimír Čunát1-8/+2
This partially reverts commit 61598203a41345042d1ed0d68fbe3466be83c6be. After update to 107 the patch is already in the src.
2022-11-17firefox, thunderbird, librewolf: Enable wayland support by defaultMartin Weinelt1-3/+2
Enabling Wayland support by default prevents use of XWayland on Wayland systems, while correctly falling back to X11 when Wayland is unavailable in the current session. With the current packaging many people unnecessarily rely on the `firefox` attribute, which is suggested by nixos-generate-config, which in turn makes their Firefox use XWayland, when it shouldn't, which causes bugs with GNOME on Wayland: https://discourse.nixos.org/t/firefox-all-black-when-first-launched-after-login/21143 Using the Wayland-enabled Firefox was tested on pure X11 systems by contributors on the #nix-mozilla:nixos.org room and we are confident this change will not cause severe regressions. Even better, people can now toggle `MOZ_ENABLE_WAYLAND=<0|1>` in their environment to override this decision, should they feel the need to do so.
2022-11-17chromiumBeta: 108.0.5359.40 -> 108.0.5359.48Michael Weiss1-3/+3
2022-11-15librewolf: 106.0.3-1 -> 107.0-1squalus1-5/+5
2022-11-14firefox-esr-102-unwrapped: 102.4.0esr -> 102.5.0esrMartin Weinelt1-2/+2
https://www.mozilla.org/en-US/firefox/102.5.0/releasenotes/
2022-11-14firefox-bin-unwrapped: 106.0.5 -> 107.0Martin Weinelt1-393/+393
https://www.mozilla.org/en-US/firefox/107.0/releasenotes/
2022-11-14firefox{,-bin}, thunderbird{,-bin}: Set meta.changelogMartin Weinelt2-0/+3
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-08-11 03:59:06 +0000