Both tests had been disabled since 2012. They could not simply be reenabled: "last-pb-context-exited" is now fired from a private context refcount kept on CanonicalBrowsingContext, which only counts content browsing contexts, so the chrome windowless browser the tests used never moved the count and the notification never fired. An attached content context cannot have its origin attributes changed either, so the context has to be created private. test_pb_notification.js now uses XPCShellContentUtils to load a private content page and closes it. test_pb_notification_ipc.js is inverted. The private context can only be created in the parent process, so the parent drives it and the child only observes, which covers the ContentParent -> ContentChild relay of the topic that the content process consumers depend on. Differential Revision: https://phabricator.services.mozilla.com/D322105
40 lines
815 B
TOML
40 lines
815 B
TOML
[DEFAULT]
|
|
head = "head_docshell.js"
|
|
support-files = [
|
|
"data/engine.xml",
|
|
"data/enginePost.xml",
|
|
"data/enginePrivate.xml",
|
|
]
|
|
|
|
["test_URIFixup.js"]
|
|
|
|
["test_URIFixup_check_host.js"]
|
|
|
|
["test_URIFixup_forced.js"]
|
|
# Disabled for 1563343 -- URI fixup should be done at the app level in GV.
|
|
|
|
["test_URIFixup_info.js"]
|
|
requesttimeoutfactor = 3 # Slow on Windows
|
|
skip-if = [
|
|
"os == 'android' && os_version == '14' && arch == 'x86_64'",
|
|
]
|
|
|
|
["test_URIFixup_search.js"]
|
|
skip-if = [
|
|
"os == 'android' && os_version == '14' && arch == 'x86_64'",
|
|
]
|
|
|
|
["test_allowJavascript.js"]
|
|
support-files = [
|
|
"AllowJavascriptChild.sys.mjs",
|
|
"AllowJavascriptParent.sys.mjs",
|
|
]
|
|
|
|
["test_browsing_context_structured_clone.js"]
|
|
|
|
["test_pb_notification.js"]
|
|
|
|
["test_privacy_transition.js"]
|
|
|
|
["test_subframe_stop_after_parent_error.js"]
|