Currently, WebRequest::getLimitOffset accepts an optional default limit, and an optional option name, as parameters.
There should be a user parameter accepted, and eventually, required, for accessing user preferences.
To clarify that the function gets the limit and offset //for a specific user//, I suggest:
[x] Create WebRequest::getLimitOffsetForUser
** Which requires a user to be passed to get the user preference for an option
[x] Convert WebRequest::getLimitOffset to a wrapper that simple uses `$wgUser`
[] Replace uses of ::getLimitOffset with ::getLimitOffsetForUser, supplying a user, since whether its needed or not depends on unknown user input
[] Deprecate ::getLimitOffset
Deployed uses of getLimitOffset:
https://codesearch.wmflabs.org/deployed/?q=getLimitOffset%5C(&i=nope&files=&repos=
[x] MediaWiki core https://gerrit.wikimedia.org/r/573033
[x] CentralNotice https://gerrit.wikimedia.org/r/c/573027
[x] Flow https://gerrit.wikimedia.org/r/c/573029
[x] ProofreadPage https://gerrit.wikimedia.org/r/c/573030
[x] Wikibase https://gerrit.wikimedia.org/r/573031