Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Bug][WebRender] Browser Chrome becomes unresponsive after force enabling #5952

Closed
bogas04-swiggy opened this issue Oct 11, 2019 · 0 comments
Labels
🐞 bug Crashes, Something isn't working, ..

Comments

@bogas04-swiggy
Copy link

bogas04-swiggy commented Oct 11, 2019

Steps to reproduce

  1. Enable WebRender from about:config
  2. Restart browser
  3. Navigate to different screens in browsers (show all tabs, settings, new tab etc.)

Expected behavior

Everything should work fine

Actual behavior

Buttons show ripple effects but they don't perform the action.

It used to be working fine until 2 days ago, since then the problem has arisen.

Screencast

Device information

  • Android device: Realme X, Android Pie (ColorOS 6.0)
Description GPU #1
Active Yes
Description Model: RMX1901, Product: RMX1901, Manufacturer: Realme, Hardware: qcom, OpenGL: Qualcomm -- Adreno (TM) 616 -- OpenGL ES 3.2 V@331.0 (GIT@01d7833, Ib6dc0f6bce) (Date:01/25/19)
Vendor ID Qualcomm
Device ID Adreno (TM) 616
Driver Version OpenGL ES 3.2 V@331.0 (GIT@01d7833, Ib6dc0f6bce) (Date:01/25/19)
  • Fenix version: Nightly 191011 13:35 (Build #12841339) 📦: 16.0.0, ab2555b20 🦎: 71.0a1-2019100409465

┆Issue is synchronized with this Jira Task

@bogas04-swiggy bogas04-swiggy added the 🐞 bug Crashes, Something isn't working, .. label Oct 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐞 bug Crashes, Something isn't working, ..
Projects
None yet
Development

No branches or pull requests

1 participant