-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[scroll-anchoring] Add release logging for scroll anchoring adjustments #22629
[scroll-anchoring] Add release logging for scroll anchoring adjustments #22629
Conversation
18f1543
to
e6676c9
Compare
EWS run on previous version of this PR (hash d7a119f)
|
EWS run on previous version of this PR (hash 18f1543)
|
EWS run on previous version of this PR (hash e6676c9)
|
@@ -369,7 +369,8 @@ void ScrollAnchoringController::adjustScrollPositionForAnchoring() | |||
} | |||
#endif | |||
auto newScrollPosition = m_owningScrollableArea.scrollPosition() + IntPoint(adjustment.width(), adjustment.height()); | |||
LOG_WITH_STREAM(ScrollAnchoring, stream << "ScrollAnchoringController::updateScrollPosition() for frame: " << frameView() << " for scroller: " << m_owningScrollableArea << " adjusting from: " << m_owningScrollableArea.scrollPosition() << " to: " << newScrollPosition); | |||
ALWAYS_LOG_WITH_STREAM(stream << "ScrollAnchoringController::updateScrollPosition() is main frame: " << frameView().frame().isMainFrame() << " for scroller: " << m_owningScrollableArea << " adjusting from: " << m_owningScrollableArea.scrollPosition() << " to: " << newScrollPosition); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(It would also be good to double check that m_owningScrollableArea
doesn't contain any sensitive information, as well)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was considering changing this to log the element of the scrollable area as well as the anchor element. Should we be concerned about logging the element (as it would show generally where the user was looking on the page) or are we just worried about logging the url?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose the elements could also have revealing class names as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, class and id names (while mostly innocuous) could potentially reveal what websites the user was visiting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right I'll split those logs into debug logs and keep just the mainframe/main scroller and scroll position logging for release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good! rs=me
e6676c9
to
5e3a11d
Compare
EWS run on current version of this PR (hash 5e3a11d) |
EWS run on current version of this PR (hash 5e3a11d) |
https://bugs.webkit.org/show_bug.cgi?id=267379 rdar://120812771 Reviewed by Wenson Hsieh. Add release logs for scroll anchoring adjusmtents for easier diagnosing of scroll anchoring bugs. * Source/WebCore/page/scrolling/ScrollAnchoringController.cpp: (WebCore::ScrollAnchoringController::adjustScrollPositionForAnchoring): Canonical link: https://commits.webkit.org/272985@main
5e3a11d
to
235f339
Compare
Committed 272985@main (235f339): https://commits.webkit.org/272985@main Reviewed commits have been landed. Closing PR #22629 and removing active labels. |
235f339
5e3a11d