Closed Bug 1374892 Opened 4 years ago Closed 4 years ago
Consider removing the ns
ISHistory Listener exception throwing machinery that shows up in Speedometer
(In reply to :Ehsan Akhgari (needinfo please, extremely long backlog) from comment #0) > Michael, what are these? Do you know? Yes, these are extra methods on the nsISHistoryListener which were added by freesamael for bug 1310761. They are used in order to listen for other changes to the local SHistory which the parent process might need to be notified about. In SessionStore, we don't need to listen to them, as they are extra. We might want to implement them anyway however, if exception handling is slower, or we might want to remove them if they won't be required by the future plans for GroupedSHistory (I'm not sure what the plans are for that - ni?-ing freesamael for that).
Flags: needinfo?(michael) → needinfo?(sawang)
I don't think we have any plans for GroupSHistory... but could we just add the 2 functions to session store, and probably also mobile/android/chrome/content/browser.js, to prevent exceptions?
OK, I'll add some dummy methods to make us not throw exceptions here. For some reason I didn't see the C++ consumer of this interface before!
Attachment #8880231 - Flags: review?(sawang) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/d7420c18c12e Implement nsISHistoryListener::OnLengthChanged/OnIndexChanged on the JS implementations to avoid generating silent exceptions when Gecko calls these functions; r=freesamael
You need to log in before you can comment on or make changes to this bug.