The fact that scroll-customization callbacks are associated with an Element rather than a node add significant complexity to scrolling code, since document-level scrolling works on the LayoutView (i.e. the Document Node, rather than Element).
This means making page/scrolling/scroll_customization_callbacks.h store a map from Node->Callback rather than Element->Callback.
Comment 1 by bugdroid1@chromium.org
, Oct 24