Some of this has been addressed elsewhere (e.g. `nsIFrame::GetOffsets` in bug 1713491). Some of it hasn't; e.g. we still have [`virtual nsresult GetChildFrameContainingOffset(`](https://searchfox.org/mozilla-central/rev/1f617334179cf28b4b310d1d116ddbc8ef3348ea/layout/generic/nsIFrame.h#2284) whose `nsresult` return value could presumably be removed (that was one of the APIs that the patch here cleans up). In any case: the patch here is unfortunately huge and would be prohibitively difficult to rebase, given the code changes over the last 12 years. So we can't use this bug/patch for much at this point other than for inspiration when rewriting these cleanups from scratch (which probably isn't high-priority). Given we're already at 79 comments here, let's just close this bug as INACTIVE and we can file new bugs as-needed for these cleanups.
Bug 243370 Comment 80 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Some of this has been addressed elsewhere (e.g. `nsIFrame::GetOffsets` in bug 1713491). Some of it hasn't; e.g. we still have [`virtual nsresult GetChildFrameContainingOffset(`](https://searchfox.org/mozilla-central/rev/1f617334179cf28b4b310d1d116ddbc8ef3348ea/layout/generic/nsIFrame.h#2284) whose `nsresult` return value could presumably be removed (that was one of the APIs that the patch here cleans up). In any case: the patch here is unfortunately huge and would be prohibitively difficult to rebase, given the code changes over the last 12 years. So we can't use this bug/patch for much at this point other than for inspiration when rewriting these cleanups from scratch (which probably isn't high-priority). Given we're already at 79 comments here, this isn't a great place to pick that work back up; let's just close this bug as INACTIVE and we can file new bugs as-needed for these cleanups.