Re: [whatwg] Expose the 'renderport' to content

On Tue, Apr 5, 2016 at 10:26 PM, Matt Woodrow wrote: > Our suggested solution to this is to add a callback to scrollable elements > that fires before painting (similar to requestAnimationFrame) and exposes > the (approximate) region of the element that the UA is going to

[whatwg] Expose the 'renderport' to content

Hi, I'd like to propose exposing the 'renderport' to web content, defined as the area of a scrollable container that is actually rendered by the UA, which may be larger than the viewport (visible) area. Most browsers these days are rendering areas larger than what is currently visible