You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Download button in the DevTools panel is experiencing a UI malfunction after visiting sub-pages of landing pages. This bug manifests as a broken UI for the button.
To Reproduce
Navigate to any website.
Open the DevTools panel and locate the cookie frame.
Verify that the Download button is displayed correctly.
Visit another landing page and explore its sub-pages (e.g., Private Advertising, Tracking Protection).
Return to the cookie frame within DevTools.
Observe the broken UI affecting the Download button.
Expected behavior
The Download button should maintain its consistent visual appearance throughout all DevTools interactions, regardless of the previously visited website pages.
Screenshots
brokendownload.mp4
Desktop (please complete the following information):
Open Tabs: 1 Active Extensions:
Privacy Sandbox Analysis Tool: ehbnpceebmgpanbbfckhoefhdibijkef
Google Docs Offline: ghbmnnjooekpmoecnnnilnnbdlolhkhi Chrome Version: Version 123.0.0.0 (x86-64) PSAT Version: 0.7.0 OS - System Architecture: MacOS (x86-64)
The text was updated successfully, but these errors were encountered:
Describe the bug
The Download button in the DevTools panel is experiencing a UI malfunction after visiting sub-pages of landing pages. This bug manifests as a broken UI for the button.
To Reproduce
Expected behavior
The Download button should maintain its consistent visual appearance throughout all DevTools interactions, regardless of the previously visited website pages.
Screenshots
brokendownload.mp4
Desktop (please complete the following information):
Open Tabs: 1
Active Extensions:
Privacy Sandbox Analysis Tool: ehbnpceebmgpanbbfckhoefhdibijkef
Google Docs Offline: ghbmnnjooekpmoecnnnilnnbdlolhkhi
Chrome Version: Version 123.0.0.0 (x86-64)
PSAT Version: 0.7.0
OS - System Architecture: MacOS (x86-64)
The text was updated successfully, but these errors were encountered: