From tobias-qutebrowser at dussa.de Tue Jan 5 16:41:19 2021 From: tobias-qutebrowser at dussa.de (Tobias Dussa) Date: Tue, 5 Jan 2021 16:41:19 +0100 Subject: [qutebrowser] Given the process ID, can I find out the loaded URL? In-Reply-To: <20201230204032.uzq7gb2awc4vuifl@aragog.localdomain> References: <20201230204032.uzq7gb2awc4vuifl@aragog.localdomain> Message-ID: Hi, On Wed, Dec 30, 2020 at 09:40:32PM +0100, Florian Bruhin wrote: > Right now, the easiest thing you can do is to send a SIGSTP to the > process and see which tab is frozen; or send a SIGTERM and see which tab > crashes. Somewhat relatedly, I just stumbled across this: https://omar.website/tabfs/ Having something like that would be totally awesome. :) Cheers, Toby. -- The Most Dangerous Things in Aviation: A pilot with a toolbox. A mechanic with a pilot's license. A stewardess with a chipped tooth. From Anthony.Boxall at element-i.de Wed Jan 20 09:01:53 2021 From: Anthony.Boxall at element-i.de (Boxall, Anthony) Date: Wed, 20 Jan 2021 08:01:53 +0000 Subject: [qutebrowser] MS Teams Message-ID: Hi. For my job I need to use Microsoft Teams at the moment during lockdown. It does not seem to work with qutebrowser. I get a message along the lines of ?this browser is not supported, try one of these...?. As qutebrowser is chromium based I expected it to work. I?d be grateful for any tips or suggestions. I?m using qutebrowser on opensuse Linux. Let me know if you need any more information. Thanks in advance, Anthony -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias-qutebrowser at dussa.de Wed Jan 20 09:08:32 2021 From: tobias-qutebrowser at dussa.de (Tobias Dussa) Date: Wed, 20 Jan 2021 09:08:32 +0100 Subject: [qutebrowser] MS Teams In-Reply-To: References: Message-ID: Hi, On Wed, Jan 20, 2021 at 08:01:53AM +0000, Boxall, Anthony wrote: > Hi. For my job I need to use Microsoft Teams at the moment during > lockdown. It does not seem to work with qutebrowser. I get a message > along the lines of ?this browser is not supported, try one of these...?. > As qutebrowser is chromium based I expected it to work. For what it's worth, qutebrowser works well for me here with MS Teams. (Erm. Okay, "works well" is a stretch, but that's not on qutebrowser, Teams just sucks IMHO.) > I?d be grateful for any tips or suggestions. I?m using qutebrowser on > opensuse Linux. Let me know if you need any more information. What problems exactly do you see? I'm running Manjaro Linux with this: --- qutebrowser v1.14.1 Git commit: Backend: QtWebEngine (Chromium 83.0.4103.122) Qt: 5.15.2 CPython: 3.9.1 PyQt: 5.15.2 --- Cheers, Toby. -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GAT d--(++) s++: a C++$ UBHL*++++$ P+++$>++++ L++++$>+++++ E(+) W+(--) N+++>$ o+ K w--- !O++ M- V PS+ PE+ Y++ PGP++$>++++ t+++@ 5-- X+ R-* tv- b++(+++)>++++ DI+++>++++ D++ G++ e+++*>++++(+++++) h---(*)>++ r+++ y++++* ------END GEEK CODE BLOCK------ From konubinix at gmail.com Wed Jan 20 09:45:59 2021 From: konubinix at gmail.com (Samuel Loury) Date: Wed, 20 Jan 2021 09:45:59 +0100 Subject: [qutebrowser] MS Teams In-Reply-To: References: Message-ID: <87pn20ov20.fsf@gmail.com> "Boxall, Anthony" writes: > Hi. For my job I need to use Microsoft Teams at the moment during > lockdown. It does not seem to work with qutebrowser. I get a message > along the lines of ?this browser is not supported, try one of > these...?. Strange... I use it from time to time and it works without problem. -- Konubinix GPG Key : 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: From timothee.floure at posteo.net Wed Jan 20 09:18:21 2021 From: timothee.floure at posteo.net (=?utf-8?B?VGltb3Row6ll?= Floure) Date: Wed, 20 Jan 2021 09:18:21 +0100 Subject: [qutebrowser] MS Teams In-Reply-To: References: Message-ID: <20210120081821.ywyok56yj4e2pgbt@phi> Hi Anthony, Not a MS Teams user, but I believe it's either - or both? - that: * MS Teams checks your user agent [1], which is a dumb string and is easily modified (I think it's the most likely case) to fool the service. * MS Teams checks for supported video codecs which are not enabled on your QtWebengine build (might be due to licensing issues with your distribution). [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent Regards from Bern, -- Timoth?e -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From me at the-compiler.org Wed Jan 20 12:14:54 2021 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 20 Jan 2021 12:14:54 +0100 Subject: [qutebrowser] MS Teams In-Reply-To: References: Message-ID: <20210120111454.nao6qurnkqiqb2ql@aragog.localdomain> Hey, On Wed, Jan 20, 2021 at 08:01:53AM +0000, Boxall, Anthony wrote: > Hi. For my job I need to use Microsoft Teams at the moment during > lockdown. It does not seem to work with qutebrowser. I get a message > along the lines of ?this browser is not supported, try one of > these...?. As qutebrowser is chromium based I expected it to work. > I?d be grateful for any tips or suggestions. I?m using qutebrowser on > opensuse Linux. Let me know if you need any more information. Like others already mentioned, no issues here either. Can you show :version? Also, can you reproduce this with --temp-basedir? Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From Anthony.Boxall at element-i.de Wed Jan 20 13:27:18 2021 From: Anthony.Boxall at element-i.de (Boxall, Anthony) Date: Wed, 20 Jan 2021 12:27:18 +0000 Subject: [qutebrowser] MS Teams In-Reply-To: <20210120111454.nao6qurnkqiqb2ql@aragog.localdomain> References: , <20210120111454.nao6qurnkqiqb2ql@aragog.localdomain> Message-ID: Thanks very much for the quick responses guys. I?m not at my computer now, but I?ll check out your emails when I?m back. Fwiw I agree, MS teams is not good ________________________________ Von: Florian Bruhin Gesendet: Mittwoch, Januar 20, 2021 12:15 PM An: Boxall, Anthony Cc: qutebrowser at lists.qutebrowser.org Betreff: Re: [qutebrowser] MS Teams Hey, On Wed, Jan 20, 2021 at 08:01:53AM +0000, Boxall, Anthony wrote: > Hi. For my job I need to use Microsoft Teams at the moment during > lockdown. It does not seem to work with qutebrowser. I get a message > along the lines of ?this browser is not supported, try one of > these...?. As qutebrowser is chromium based I expected it to work. > I?d be grateful for any tips or suggestions. I?m using qutebrowser on > opensuse Linux. Let me know if you need any more information. Like others already mentioned, no issues here either. Can you show :version? Also, can you reproduce this with --temp-basedir? Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Thu Jan 28 11:48:17 2021 From: me at the-compiler.org (Florian Bruhin) Date: Thu, 28 Jan 2021 11:48:17 +0100 Subject: [qutebrowser] qutebrowser v2.0.0 released (with better adblocker)! Message-ID: <20210128104817.ljsjkjoxtp73e3k7@aragog.localdomain> Hey, I'm very happy to announce that I released qutebrowser v2.0.0 today! This release integrates Brave's Rust adblocking library if the "adblock" Python library is available. It also drops support for old Qt/Python versions and comes with various other dependency changes. This has been a rather long release cycle - so far, feature releases have happened all two months or so, but v1.14.0 was released back in October (with a patch release in December). Thus, this release includes a *lot* of new features, bugfixes and other changes as well. It's a big milestone in many ways, and a lot of things changed: $ git --no-pager diff --stat v1.14.1..v2.0.0 [...] 548 files changed, 13186 insertions(+), 10871 deletions(-) Thanks to everyone involved, especially ?rni Dagur for the excellent work on the adblocking integration! Here's the full changelog: Major changes ~~~~~~~~~~~~~ - If the Python `adblock` library is available, it is now used to integrate Brave's Rust adblocker library for improved adblocking based on ABP-like filter lists (such as EasyList). If it is unavailable, qutebrowser falls back to host-blocking, i.e. the same blocking technique it used before this release. As part of this, various settings got renamed, see "Changed" below. **Note: If the `adblock` dependency is available, qutebrowser will ignore custom host blocking** via the `blocked-hosts` config file or `file:///` URLs supplied as host blocking lists. You will need to either migrate those to ABP-like lists, or set `content.blocking.method` to `both`. - Various dependency upgrades - a quick checklist for packagers (see "Changed" below for details): * Ensure you're providing at least Python 3.6.1. * Ensure you're providing at least Qt 5.12 and PyQt 5.12. * Add a new optional dependency on the Python `adblock` library (if packaged - if not, consider packaging it, albeit optional it's very useful for users). * Remove the `cssutils` optional dependency (if present). * Remove the `attrs` (`attr`) dependency. * Remove the `pypeg2` dependency (and perhaps consider dropping the package if not used elsewhere - it's https://fdik.org/pyPEG2/[inactive upstream] and the repository was removed by Bitbucket). * Move the `pygments` dependency from required to optional. * Move the `setuptools` dependency from runtime (for `pkg_resources`) to build-time. * For Python 3.6, 3.7 or 3.8, add a dependency on the `importlib_resources` backport. * For Python 3.6 only, add a dependency on the `dataclasses` backport. - Dropped support for old OS versions in binary releases: * Support for Windows 7 is dropped in the Windows binaries, the minimum required Windows version is now Windows 8.1. * Support for macOS 10.13 High Sierra is dropped in the macOS binaries, the minimum required macOS version is now macOS 10.14 Mojave. - Various renamed settings and commands, see "Deprecated" and "Changed" below. Removed ~~~~~~~ - The `--enable-webengine-inspector` flag (which was only needed for Qt 5.10 and below) is now dropped. With Qt 5.11 and newer, the inspector/devtools are enabled unconditionally. - Support for moving qutebrowser data from versions before v1.0.0 has been removed. - The `--old` flag for `:config-diff` has been removed. It used to show customized options for the old pre-v1.0 config files (in order to aid migration to v1.0). - The `:inspector` command which was deprecated in v1.13.0 (in favor of `:devtools`) is now removed. Deprecated ~~~~~~~~~~ - Several commands have been renamed for consistency and/or easier grouping of related commands. Their old names are still available, but deprecated and will be removed in qutebrowser v2.1.0. * `run-macro` -> `macro-run` * `record-macro` -> `macro-record` * `buffer` -> `tab-select` * `open-editor` -> `edit-text` * `toggle-selection` -> `selection-toggle` * `drop-selection` -> `selection-drop` * `reverse-selection` -> `selection-reverse` * `follow-selected` -> `selection-follow` * `follow-hint` -> `hint-follow` * `enter-mode` -> `mode-enter` * `leave-mode` -> `mode-leave` Added ~~~~~ - New settings for the ABP-based adblocker: * `content.blocking.method` to decide which blocker(s) should be used. * `content.blocking.adblock.lists` to configure ABP-like lists to use. - New `qt.environ` setting which makes it easier to set/unset environment variables for qutebrowser. - New settings to use an external file picker (such as ranger or vifm): * `fileselect.handler` (`default` or `external`) * `fileselect.multiple_files.command` * `fileselect.single_file.command` - When QtWebEngine has been updated but PyQtWebEngine hasn't yet, the dark mode settings might stop working. As a (currently undocumented) escape hatch, this version adds a `QUTE_DARKMODE_VARIANT=qt_515_2` environment variable which can be set to get the correct behavior in (transitive) situations like this. - New `--desktop-file-name` commandline argument, which can be used to customize the desktop filename passed to Qt (which is used to set the `app_id` on Wayland). - The `:open` completion now also completes local file paths and `file://` URLs, via a new `filesystem` entry in `completion.open_categories`. Also, a new `completion.favorite_paths` setting was added which can be used to add paths to show when `:open` is used without any input. - New `QUTE_VERSION` variable for userscripts, which can be used to read qutebrowser's version. - New "Copy URL" entry in the context menu for downloads. - New `:bookmark-list` command which lists all bookmarks/quickmarks. The corresponding `qute://bookmarks` URL already existed since v0.8.0, but it was never exposed as a command. - New `qt.workarounds.remove_service_workers` setting which can be used to remove the "Service Workers" directory on every start. Usage of this option is generally discouraged, except in situations where the underlying QtWebEngine bug is a known cause for crashes. - Changelogs are now shown after qutebrowser was upgraded. By default, the changelog is only shown after minor upgrades (feature releases) but not patch releases. This can be adjusted (or disabled entirely) via a new `changelog_after_upgrade` setting. - New userscripts: * `kodi` to play videos in Kodi * `qr` to generate a QR code of the current URL * `add-nextcloud-bookmarks` to create bookmarks in Nextcloud's Bookmarks app * `add-nextcloud-cookbook` to add recipes to Nextcloud's Cookbook app Changed ~~~~~~~ - `config.py` files now are required to have either `config.load_autoconfig(False)` (don't load `autoconfig.yml`) or `config.load_autoconfig()` (do load `autoconfig.yml`) in them. - Various host-blocking settings have been renamed to accomodate the new ABP-like adblocker: * `content.host_blocking.enabled` -> `content.blocking.enabled` (controlling both blockers) * `content.host_blocking.whitelist` -> `content.blocking.whitelist` (controlling both blockers) * `content.host_blocking.lists` -> `content.blocking.hosts.lists` - Changes to default settings: * `tabs.background` is now `true` by default, so that new tabs get opened in the background. * `input.partial_timeout` is now set to 0 by default, so that partially typed key strings are never cleared. * `hints.leave_on_load` is now `false` by default, so that hint mode doesn't get left when a page finishes loading. This can lead to stale hints persisting in rare circumstances, but is better than leaving hint mode when the user entered it before loading was completed. * The default for `tabs.width` (tab bar width if vertical) is now 15% of the window width rather than 20%. * The default bindings for moving tabs (`tab-move -` and `tab-move +`) were changed from `gl` and `gr` to `gK` and `gJ`, to be consistent with the tab switching bindings. * The text color for warning messages is now black instead of white, for increased contrast and thus readability. * The default timeout for messages is now raised from 2s to 3s. - On the first start, the history completion database is regenerated to remove a few problematic entries (such as long `qute://pdfjs` URLs). This might take a couple of minutes, but is a one-time operation. This should result in a performance improvement for the completion for affected users. - qutebrowser now shows an error if its history database version is newer than expected. This currently should never happen, but allows for potentially backwards-incompatible changes in future versions. - At least Python 3.6.1 is now required to run qutebrowser, support for Python 3.5 (and 3.6.0) is dropped. Note that Python 3.5 is https://www.python.org/downloads/release/python-3510/[no longer supported upstream] since September 2020. - At least Qt/PyQt 5.12 is now required to run qutebrowser, support for 5.7 to 5.11 (inclusive) is dropped. While Debian Buster ships Qt 5.11, it's based on a Chromium version from 2018 with https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#browser-security[no Debian security support] and unsupported upstream since May 2019. It also has compatibility issues with various websites (GitHub, Twitch, Android Developer documentation, YouTube, ...). Since no newer Debian Stable is released at the time of writing, it's recommended to https://github.com/qutebrowser/qutebrowser/blob/master/doc/install.asciidoc#installing-qutebrowser-with-virtualenv[install qutebrowser in a virtualenv] with a newer version of Qt/PyQt. - New optional dependency on the Python `adblock` library (see above for details). - The (formerly optional) `cssutils` dependency is now removed. It was only needed for improved behavior in corner cases when using `:download --mhtml` with the (non-default) QtWebKit backend, and as such it's unlikely anyone is still relying on it. The `cssutils` project is also dead upstream, with its repository being gone after Bitbucket https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket[removed Mercurial support]. - The (formerly required) `pygments` dependency is now optional. It is only used when using `:view-source` with QtWebKit, or when forcing it via `:view-source --pygments` on QtWebEngine. If it is unavailable, an unhighlighted fallback version of the page's source is shown. - The former runtime dependency on the `pkg_resources` module (part of the `setuptools` project) got dropped. Note that `setuptools` is still required to run `setup.py`. - A new dependency on the `importlib_resources` module got introduced for Python versions up to and including 3.8. Note that the stdlib `importlib.resources` module for Python 3.7 and 3.8 is missing the needed APIs, thus requiring the backports for those versions as well. - The former dependency on the `attrs`/`attr` package is now dropped in favour of `dataclasses` in the Python standard library. On Python 3.6, a new dependency on the `dataclasses` backport is now required. - The former dependency on the `pypeg2` package is now dropped. This might cause some changes for certain corner-cases for suggested filenames when downloading files with the QtWebKit backend. - Windows and macOS releases now ship Python 3.9 rather than 3.7. - The `colors.webpage.darkmode.*` settings are now also supported with older Qt versions (Qt 5.12 and 5.13) rather than just with Qt 5.14 and above. - For regexes in the config (`hints.{prev,next}_regexes`), certain patterns which will change meanings in future Python versions are now disallowed. This is the case for character sets starting with a literal `[` or containing literal character sequences `--`, `&&`, `~~`, or `||`. To avoid a warning, remove the duplicate characters or escape them with a backslash. - If `prompt(..., "default")` is used via JS, the default text is now pre-selected in the prompt shown by qutebrowser. - URLs such as `::1/foo` are now handled as a search term or local file rather than IPv6. Use `[::1]/foo` to force parsing as IPv6 instead. - The `mkvenv.py` script now runs a "smoke test" after setting up the virtual environment to ensure it's working as expected. If necessary, the test can be skipped via a new `--skip-smoke-test` flag. - Both qutebrowser userscripts and Greasemonkey scripts are now additionally picked up from qutebrowser's config directory (the `userscripts` and `greasemonkey` subdirectories of e.g. `~/.config/qutebrowser/`) rather than only the data directory (the same subdirectories of e.g. `~/.local/share/qutebrowser/`). - The `:later` command now understands a time specification like `5m` or `1h5m2s`, rather than just taking milliseconds. - The `importer.py` script doesn't use a browser argument anymore; instead its `--input-format` switch can be used to configure the input format. The help also was expanded to explain how to use it properly. - If `tabs.tabs_are_windows` is set, the `tabs.last_close` setting is now ignored and the window is always closed when using `:close` (`d`). - With the (default) QtWebEngine backend, if a custom `accept` header is set via `content.headers.custom`, the custom value is now ignored for XHR (`XMLHttpRequest`) requests. Instead, the sent value is now `*/*` or the header set from JavaScript, as it would be if `content.headers.custom` wasn't set. - The `:tab-select` completion now shows the underlying renderer process PID if doing so is supported (on QtWebEngine 5.15). - If `tabs.favicons.show` is set to `never`, favicons aren't unnecessarily downloaded anymore. Thus, disabling favicons can help with a possible https://www.ghacks.net/2021/01/22/favicons-may-be-used-to-track-users/[fingerprinting vector]. - "Super" is now understood as a modifier (i.e. as alias to "Meta"). - Initial support for Python 3.10 (currently in Alpha stage). - Various performance improvements, including for the startup time. Fixed ~~~~~ - With interpolated color settings (`colors.tabs.indicator.*` and `colors.downloads.*`), the alpha channel is now handled correctly. - Fixes to userscripts: * `format_json` now uses `env` in its shebang, making it work correctly on systems where `bash` isn't located in `/bin`. * `qute-pass` now handles the MIME output format introduced in gopass 1.10.0. * `qute-lastpass` now types multiple `<` or `>` characters correctly. - The `:undo` completion now sorts its entries correctly (by the numerical index rather than lexicographically). - The `completion.web_history.ignore` setting now works properly when set in `config.py` (rather than via `:set`). Additionally, a `:config-source` will not result in a history rebuild if the value wasn't actually changed. - When downloading a `data:` URL, the suggested filename is now improved and contains a proper extension. Before this fix, qutebrowser would use the URL's data contents as filename with QtWebEngine; or "binary blob" with the Qt network stack. - When `:tab-only` is run before a tab is available, an error is now shown instead of crashing. - A couple of long URLs (such as `qute://pdfjs` URLs) are now not added to the history database anymore. - A bug in QtWebEngine 5.15.2 causes "renderer process killed" errors on websites like LinkedIn and TradingView. There is now a workaround in qutebrowser to prevent this from happening. - Nextcloud Calendars started using `String.replaceAll` which was only added to Chromium recently (Chrome 85), so won't work with current QtWebEngine versions. This release includes a workaround (a polyfill as a site-specific-quirk). Enjoy, and as usual, let me know if there are any issues! Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From me at the-compiler.org Thu Jan 28 18:02:18 2021 From: me at the-compiler.org (Florian Bruhin) Date: Thu, 28 Jan 2021 18:02:18 +0100 Subject: [qutebrowser] qutebrowser v2.0.1 released! In-Reply-To: <20210128104817.ljsjkjoxtp73e3k7@aragog.localdomain> References: <20210128104817.ljsjkjoxtp73e3k7@aragog.localdomain> Message-ID: <20210128170218.iyf6vdbwqkcj4flu@aragog.localdomain> Heya, Looks like the v2.0.0 release went big on Hacker News: https://news.ycombinator.com/item?id=25940453 As those things usually go, a couple of regressions were reported shortly after the v2.0.0 release. I've spent the day squashing a couple of bugs and just released v2.0.1 because some of them prevented qutebrowser from starting properly (though only if it was installed in a particular way; or if it was installed/packaged in an unclean way). Considerably less changes this time: 19 files changed, 171 insertions(+), 25 deletions(-) And the changelog is much shorter as well: Fixed ~~~~~ - If qutebrowser was installed as a Python egg (similar to a .zip file, via `setup.py install` under certain conditions), a change in v2.0.0 caused it to not start properly. This is now fixed. - If qutebrowser was set up (or packaged) in an unclean environment, this could result in a stale `qutebrowser/components/adblock.py` file being picked up. That file is not part of the release anymore, but if an old version is still around, causes qutebrowser to crash. It's now explicitly blocked inside qutebrowser so it gets ignored even if it still exists. - When the adblocking method was switched using `:set`, and the `adblock` dependency was unavailable when qutebrowser started (but was installed while qutebrowser was open), this resulted in a crash. Now a warning prompting for a restart of qutebrowser is shown instead. Changed ~~~~~~~ - The `format_json` userscript now uses sh instead of bash again. - The `add-nextcloud-bookmarks`, `add-nextcloud-cookbook`, `readability` and `ripbang` userscripts now use a `python3` rather than plain `python` shebang. - When `QTWEBENGINE_CHROMIUM_FLAGS` is set in the environment, this causes flag handling (including workarounds for QtWebEngine crashes) inside qutebrowser to break. This will be handled properly in a future version, but this release now shows a warning on standard output if this is the case. - The config completion for `fileselect.*.command` now also includes the "nnn" terminal file manager. Now back to reading Reddit/Hackernews comments, Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From john at lane.uk.net Sat Jan 30 12:23:01 2021 From: john at lane.uk.net (John Lane) Date: Sat, 30 Jan 2021 11:23:01 +0000 Subject: [qutebrowser] MS Teams In-Reply-To: References: Message-ID: For what it's worth... there is a linux client and that does work ok, at least on my Arch box. It is just an electron version of the web app so hasn't the features of the client on other OSs but it does work ok (well, as well as its implementation allows but that a whole other story...). On 20/01/2021 08:01, Boxall, Anthony wrote: > Hi. For my job I need to use Microsoft Teams at the moment during > lockdown. It does not seem to work with qutebrowser. I get a message > along the lines of ?this browser is not supported, try one of > these...?. As qutebrowser is chromium based I expected it to work.? > I?d be grateful for any tips or suggestions. I?m using qutebrowser on > opensuse Linux. Let me know if you need any more information.? > > Thanks in advance, > Anthony