We were incorrectly calling presentMetalFrame while force-cpu-painting was enabled, so updateLayer never had any chance to be called. However, in addition to that, it turned out that there's a subclass of CALayer that is used by NSView by default which cannot be created in a makeBackingLayer override, so updateLayer was never going to be called anyway. In order to update the layer at the requisite time, a new LadybirdWebViewContentLayer had to be added to simply call the delegate on our view. Setting the contentsRect on the layer was also incorrect, and caused the contents to shift and stretch until WebContent's backing stores shrank to fit the new view size. |
||
|---|---|---|
| .. | ||
| Android | ||
| AppKit | ||
| cmake | ||
| Icons | ||
| Qt | ||
| .gitignore | ||
| CMakeLists.txt | ||
| Info.plist | ||