Hunt for UI bugs due to WebRender

Hunt from Home, Mozilla karnataka! UI Bug Hunting

Featured image

Every developer would agree to the fact that, your code is Incomplete if you never encountered bugs. Irrespective of when it would’ve arised, the satisfaction you get after resolving them is unbeatable, as it helps you move towards “Perfection” or atleast help you get better and design an experience for your user.

It’s important that we celebrate these bugs and embrace the positive change they bring in us eventually. In this work, we would focus on UI bugs and the methodology which you could use to do your part of contribution. Before we go ahead, you’d require to understand what is Rendering Engine.

What is rendering engine?

It takes HTML code and interprets it into what you see visually. For instance, a tag would be interpreted by the rendering engine as a set of instructions to make the text inside of the element bold

The rendering engine has a very important job as it displays what you see on your screen. It communicates with the networking layer of the browser to grab HTML code and other items passed from a remote server.

While Google, Opera and their variants use blink as their rendering engine which accounts 43% of usage, whilst Internet explorer uses Trident(25.8%>, Firefox and it’s variants uses Gecko(18.22%), whereas Safari uses Webkit. source

Here are steps below following which you could contribute:

join the Event on 16th May,2020 from 5:30 PM IST to 6:30 PM IST via this link

This post was authored by Ujwal Kumar and Shresth Singh . For any queries you can also contact Ravi Jain.