Kai O'Reilly
Kai O'Reilly
Here is some profiling data from scrolling on our initial release blog post in Chrome on macOS: * 65.3% of time is spent on widget rendering (not involving system rendering,...
By use of print statements, I can definitively affirm that LayoutStdLR is happening during scrolling. Different things may be more of a bottleneck on web versus other platforms; it is...
An actual `WidgetBase.NeedsLayout` is not happening however.
I am stating that I added a print statement to NeedsLayout, which is not being activated. The same is true for layoutScene, so I will redo my testing. LayoutStdLR was...
We decided on putting profile in the settings menu (you can also press Ctrl+Alt+R in the settings window), but I am fine moving it to the main menu instead.
I redid my web profiling and there was no more `layoutScene`, but there was still LayoutStdLR, with almost all of it coming from `core.Text`.
This is very troubling: it is decisively not calling `configTextSize` during scrolling on native macOS but it is calling it all the time while scrolling on web.
Somehow it keeps getting the `Scene.needsLayout` flag.
The text editors are causing it to repeatedly call `layoutScene` but only on web!
The toolbar overflow menu is triggering the layout calls!