Issue 1994: Properties in window.navigator do not survive GC
http://code.google.com/p/chromium/issues/detail?id=1994
Comment #4 by [EMAIL PROTECTED]:
So, this is not a real issue. WebKit handles JS objects for DOM nodes (such
as
HTMLElement) and non-nodes (such as History, Locaiton, Navigator)
differently. JS
wrappers of non-nodes do not survive GC if there is no references from JS
objects to
them. JS wrappers of DOM nodes are kept alive as long as nodes are in a
document tree
and document is in use.
If the property is set on window.history, window.menubar,
window.locationBar, etc
(exception window.location and window.navigator), these properties won't
exist after
a GC. Safari happens to implement window.location and window.navigator
differently
from other objects listed above, and it is an coincident that the program
mentioned
works in Safari.
So I'd suggest not to fix this issue, the author should avoid stick values
on these
windows properties.
Issue attribute updates:
Status: Available
Owner: [EMAIL PROTECTED]
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
