[iOS][WK2] Fix small bugs of dynamicViewportSizeUpdate that were causing inaccuracies in the computed target
Created attachment 234310 [details]
Comment on attachment 234310 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=234310&action=review
> + The first issue is that the unobscured content size was stored on integer coordinates. Because of that, it was
"on" should be "in"
> + on floating point. Since ARM64 does all those computation on double in the UIProcess, the value would be quite
computation*s* and double*s*
> + valid to have an exposed rect outside the page bounds, that areas is just under the obscured insets.
area, not areas
Committed r170773: <http://trac.webkit.org/changeset/170773>