| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
min_insets_.top = std::max(min_insets_.top, min);Do we want "max" or more like "add" here? If I am calling it with two toolbars on top of each others, going from 10pt to 50pt each, shouldn't the result be 20 to 100?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
Do we want "max" or more like "add" here? If I am calling it with two toolbars on top of each others, going from 10pt to 50pt each, shouldn't the result be 20 to 100?
Yeah, I think you're right. I was originally thinking that the toolbars would need to know not just their min / max height, but where over top of the WebView they are. But I think it is easier for them to just know their min/max height and report that amount, and then it can be added together.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[ios] Add InvalidateInsetRange() to FullscreenBrowserAgent
FullscreenBrowserAgent now keeps track of the min and max top and bottom
obscured insets. When InvalidateInsetRange() is called, it zeroes out
the current tracked insets and notifies its observers by calling
WillUpdateObscuredInsetRange().
Observers can respond by calling AddObscuredInsetRange() with the
UIRectEdge (top or bottom) and the amount obscured. The browser agent
then determines and stores the maximum of the newly provided min and max
inset values compared to its current tracked values. It provides public
accessors min_insets() and max_insets() to retrieve the resulting
values.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |