Skip to Content

Chrome Incognito Tab Glitch on HP Elite Dragonfly Chromebook: Problem and Solution

A deep dive into the recent Chrome Incognito tab bug on the HP Elite Dragonfly Chromebook (Brya/Redrix), its technical roots, and practical solutions for users and developers.
27 January 2026 by
TechStora Editorial Board

Introduction

Earlier today a bug report surfaced showing that Chrome’s Incognito tabs behave oddly on the HP Elite Dragonfly 13.5" Chromebook, codename Brya (Redrix). The report includes two screenshots taken before and after a Chrome OS developer‑channel upgrade (from 145.0.7587.4 to 146.0.7634.0). While the device runs a 12th‑gen Intel Alder Lake‑U processor, the anomaly appears tied to UI changes rather than raw hardware performance.

The Reported Problem

Users observed that in Incognito mode the status bar and taskbar layout diverge from the expected ChromeOS experience. Specific quirks include:

  • A taller status bar that mirrors tablet/phone desktop mode, showing seconds, date, and a cluster of Android icons (battery, Wi‑Fi, notification bell, language indicator, Gemini, screen‑recorder).
  • A modified mouse cursor with a trailing effect.
  • The Extensions button appears, even though it is typically reserved for the desktop Chrome browser.
  • Split‑screen multitasking visuals that differ from the standard ChromeOS layout.

These visual inconsistencies can confuse users, especially when switching between regular and Incognito windows, and may hint at deeper integration issues between Chrome’s Android UI layer and ChromeOS’s native shell.

Technical Context

The HP Elite Dragonfly Chromebook runs the ALOS ZL1A.260119.001.A1 build, which blends Android 12 (API level 33) components with ChromeOS. The “Brya” platform is designed to optimize large‑screen Android experiences, but the recent developer‑channel upgrade introduced UI elements that were previously exclusive to Android tablets.

Key technical factors include:

  • The ChromeOS‑Android bridge (ARC++) that renders Android UI inside ChromeOS windows.
  • A recent status‑bar redesign intended for larger displays, now unintentionally applied to Incognito tabs.
  • Cursor rendering changes that add a “tail” effect, likely a visual experiment that leaked into the stable UI.

Potential Solutions

Both short‑term workarounds and longer‑term fixes are viable:

  • Rollback to the previous Chrome build: Reverting to 145.0.7587.4 restores the classic UI, though it sacrifices any security patches introduced in 146.
  • Disable Android UI overlays: Using chrome://flags, toggle “Enable Android status bar on large screens” (if available) to suppress the taller bar.
  • Force desktop Chrome UI: Launch Chrome with the --disable-features=ArcUi flag to keep the taskbar and cursor in their default states.
  • Report and monitor: Submit detailed logs via chrome://crash and follow the Chromium bug tracker for updates; developers often prioritize fixes based on reproducible reports.

What Users Can Do Now

Until an official patch lands, users should consider the following steps:

  • Backup any critical data and create a restore point.
  • Switch to a stable ChromeOS channel if the dev channel isn’t required for daily work.
  • Use regular (non‑Incognito) windows for tasks that rely heavily on split‑screen multitasking.
  • Keep the device’s firmware up to date, as firmware patches sometimes address UI rendering bugs.

Outlook

The Chrome team has acknowledged the issue in internal forums, noting that the UI changes were part of an experimental rollout for “large‑screen Android experiences.” A fix is expected in an upcoming developer‑channel update, likely reverting the status‑bar behavior for Incognito tabs while preserving the new design for native ChromeOS windows.

In the meantime, the community’s feedback will be crucial. By providing reproducible steps and system logs, users can help accelerate the resolution.

Take Action

If you’re experiencing the Incognito UI glitch on your HP Elite Dragonfly Chromebook, try the workarounds above and report your findings. Your input directly contributes to a smoother ChromeOS experience for everyone.

Stay informed, stay secure—join the conversation on the Chromium bug tracker today.