From bug 189719: Any idea when nsWidget::SetCursor is called? If ever, could you file a bug on making it have the same functionality as nsWindow::SetCursor?

nsWidget is the parent class for all of the various widgets in the widget/ code. Since the only widget that we use right now is nsWindow, there's no reason to implement it. Just leave it be. :)

The problem is that these two methods are out of sync. nsWindow:SetCursor seems to be more recent.

How are they out of sync?

e.g. nsWidget:SetCursor doesn't support custom icons loaded from static data

My point was that nsWidget::SetCursor is never used - only nsWindow::SetCursor does and that can load cursors from static data.

I see, but why don't we get rid of that additional code in nsWidget:SetCursor ?