LibWeb: Move away from direct usages of Gfx::Painter where possible
circl-lastname opened this issue · 0 comments
circl-lastname commented
This causes the rendering to occur on the CPU and via the Gfx::Painter even if the user chooses a different rendering backend.
We currently lack a proper API for imperative painting that uses the correct renderer, which might be needed in these cases, however creating one would be temporary as the internal graphics API may at some point receive a major rewrite to better suit the requirements of the browser.