# Switching Tabs Disables Typing Ability **URL:** \ **Category:** Desktop Support\ **Tags:** linux, bug, browser\ **Created:** [September 26, 2026, 1:06am UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772 "2026-09-26T01:06:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![BlueRobin](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@BlueRobin](https://community.brave.app/u/BlueRobin)\ **Post date:** [September 26, 2026, 1:06am UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772/1 "2026-09-26T01:06:16Z")
**Description of the issue:** **How can this issue be reproduced?** 1. Switch Tabs 2. Attempt typing in the same location as before 3. Attempt clicking in the place that you want to type, and type **Expected result:** You cannot type in the window **Brave Version( check `About Brave`):** [Brave 1.95.104 (Official Build) (x86\_64)](https://brave.com/latest/) Chromium: 153.0.8010.53 **Additional Information:** - On Fedora Linux - OS: Fedora Linux 44, x86\_64 - Desktop environment: KDE Plasma - Display server: Wayland - The issue occurs after switching away from a Brave tab and then returning to it. - The text field still appears focused; however, keyboard input is not accepted in the previously focused field. - Clicking the text field again does not restore keyboard input. - Pressing `Ctrl+L` to focus the address bar and then returning focus to the page can restore typing. - Not specific to one website - Running the ozone-platform as x-11 seems to mitigate the issue but I need to keep testing: `flatpak run com.brave.Browser --ozone-platform=x11` ---
**Author:** ![caldercay](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@caldercay](https://community.brave.app/u/caldercay)\ **Post date:** [September 26, 2026, 1:47pm UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772/2 "2026-09-26T13:47:00Z")
Welcome to the forum ! 👍 I tested using these versions: Stable: Brave 1.96.59, Chromium: 154.0.8037.58 Beta: Brave 1.97.47, Chromium: 154.0.8037.58 I tested both of those releases on **two** different installs of **openSUSE Leap** (Linux, of course). I also use **KDE Plasma** … I primarily use **X11** … but I did login using “Plasma / wayland” (wayland is buggy, why I use X11) to test for the issue. All works fine. I see you’re running an older version of Stable … do you not check for updates using your Fedora system? Oh yea, one thing I read in your last bullet point. That is VERY important information that you did not provide up top about the “version” of Brave you’re using. You’re using a Flatpak version, correct? There is a possibility of “doesn’t work like the native installation”. . What we find at the Brave download / install webpage: > [@](#): > > **Flatpak** > > Brave is available as a [Flatpak package](https://flathub.org/apps/com.brave.Browser) from Flathub. While it is maintained by Brave Software, > > ====\> it is [not yet working as well](https://github.com/flathub/com.brave.Browser/issues?q=is%3Aopen+is%3Aissue) as our native packages. \<==== > > In addition, > ====\> it modifies Chromium sandboxing in ways which have not been vetted by the Brave or Chromium security teams. \<==== > > 👍 We currently recommend that users who are able to use our official package repositories do so instead of using the Flatpak. 👍 . BTW … I’m not associated with Brave … simply a long-time user of the browser ( my other browser is Chrome ). ---
**Author:** ![BlueRobin](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@BlueRobin](https://community.brave.app/u/BlueRobin)\ **Post date:** [September 28, 2026, 2:03pm UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772/3 "2026-09-28T14:03:49Z")
The odd thing is that the flatpack version works (when running it with --ozone-platform=x11); however, **I do not use flatpack normally** and instead use KDE’s discovery center. ---
**Author:** ![caldercay](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@caldercay](https://community.brave.app/u/caldercay)\ **Post date:** [September 29, 2026, 2:09pm UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772/4 "2026-09-29T14:09:57Z")
> [@](#): > > @BlueRobin wrote: > > 1. The odd thing is that the flatpack version works (when running it with --ozone-platform=x11); > > 2. however, **I do not use flatpack normally** … > > 3. and instead use KDE’s discovery center. 1. So running with the “–ozone-platform=x11” option | argument , suggests there’s an issue on your system using **Brave** and **Wayland**. 2. Then the information you provided is in conflict with what you wrote for #2. In your last bullet point you wrote: " I need to keep testing: `flatpak run com.brave.Browser` …" states you’re strictly running using the Flatpak version. 3. Unfortunately, I’m a bit confused by that statement. Are you referring to the “ **Discover** ” software management application? (which has a special focus on Flatpak apps and BIOS updates). . Can you clarify what this statement means: “and instead use KDE’s discovery center” … you use it “how”?? ---
**Author:** ![BlueRobin](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@BlueRobin](https://community.brave.app/u/BlueRobin)\ **Post date:** [September 30, 2026, 1:44pm UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772/5 "2026-09-30T13:44:42Z")
1. Yeah it’s probably something with that 2. Not when I have the issue; I used flatpak to fix the issue via --ozone-platform=x11 3. [https://apps.kde.org/discover/](https://apps.kde.org/discover/) (is what I normally use for Brave) ---
**Author:** ![caldercay](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@caldercay](https://community.brave.app/u/caldercay)\ **Post date:** [October 1, 2026, 4:19pm UTC](https://community.brave.app/t/switching-tabs-disables-typing-ability/658772/6 "2026-10-01T16:19:10Z")
> [@](#): > > @BlueRobin wrote: > > 1. [https://apps.kde.org/discover/](https://apps.kde.org/discover/) (is what I normally use for Brave) To me, that still doesn’t make sense. I’ve been using **Discover** for **years** … I only use it to **install** Flatpak software and to **update** the machine’s BIOS. “What is it you do” with **Discover** for Brave? Update Brave to the next version? Something else?