firing pageshow/pagehide when users change tabs
Myk Melez
and forwards in history. It seems like it would make sense to also fire
those events when users change tabs, since changing tabs has the same
effect as changing one's place in history: one page gets hidden while
another gets revealed.
And it seems like pages which want to do something when revealed (like
update their content) would want to do it whether they were revealed by
history traversal or tab activation.
A corollary benefit would be that extensions which want to do something
whenever a page is focused would only have to listen for pageshow. They
wouldn't have to also implement a web progress listener that listens for
onLocationChange.
Thoughts?
-myk
Eric Shepherd
Eric Shepherd
Developer Documentation Lead
she...@mozilla.com
Tony Chang
> A corollary benefit would be that extensions which want to do something
> whenever a page is focused would only have to listen for pageshow. They
> wouldn't have to also implement a web progress listener that listens for
> onLocationChange.
Hmm? I normally listen for the select event on the tabbox in addition to
pageshow. Extensions that already do this would have to do version
checking to make sure things don't fire twice.
Tony
Myk Melez
> Hmm? I normally listen for the select event on the tabbox in addition to
> pageshow. Extensions that already do this would have to do version
> checking to make sure things don't fire twice.
Right, as would extensions like Microsummary Buddy which listen for
onLocationChange to accomplish the same effect. But once updated, such
extensions would sport much simpler code.
-myk