> There's a fundamental problem here that ROs are presuming a single rect per element. Yes, RO does not observe fragments. The reason is implementation constraints: - currently only Edge layout engine uses fragments internally. Without engine support, observing fragments cannot be done efficiently. - most of the web content does not involve fragments, and observing traditional css rect works well enough for this case. I regret that we were also unable to observe other CSS rects (border box, padding box) for performance reasons. I can imagine v2 of the API being extended to support these and maybe fragments. > I also wonder if many of the prospective use cases for this wouldn't be better handled with custom layout worklets. Layout worklets can solve the same problem, but would be more complex. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/187#issuecomment-369388813
Received on Wednesday, 28 February 2018 21:28:03 UTC