Closed Bug 594493 Opened 14 years ago Closed 14 years ago

nsIDocShell.isActive should be set for chrome pages

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: azakai, Unassigned)

References

Details

Currently we do so only for content. Doing it for chrome would enable chrome pages with html images to have their animations frozen, and in the future other fun stuff.
Blocks: 567339
Currently nsDocShell::SetIsActive doesn't allowing changing the active status of chrome docshell's, see 
http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsDocShell.cpp#4767
Alon meant local (chrome or inprocess web pages) not the chrome window itself. And I led him astray by telling him Fennec only called isActive for remote (out of process) web pages.

Truth is, we do it for both. The message manager approach works fine for local and remote pages. Sorry for the confusion. Closing bug.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.