These low level docs are getting out of date and causing confusion. Further,
they are of limited value at this stage anyway.
MozReview-Commit-ID: FSoNniNZjtj
--HG--
extra : rebase_source : fa5e02a771adcae9b0e53bd18c4eb10ebb5315ef
This test verifies that WebExt messaging works as expected for both the
background page scripts and content scripts when RDM is used.
MozReview-Commit-ID: 3fODg3nYLr7
--HG--
extra : rebase_source : ad0051f6c377f15dbe27cf6cac5c3fd07af6fac7
WebExt messaging sends several new message types to content that should be
tunneled by RDM.
This change allows them to reach content as expected in RDM mode.
MozReview-Commit-ID: GKelgOGBUKI
--HG--
extra : rebase_source : 77288fc586efbaeb9b4c344a291c7c5f815e1a15
Sometime during Firefox 56, the `dataTransfer` property was removed, so this
started to fail. It was a bit strange anyway, since we have a principal on the
outer browser.
Adds a test to cover this use case.
MozReview-Commit-ID: 9UOCc77ZRxk
--HG--
extra : rebase_source : f743c7704ff8fc0e52b7facb11e0e9b6aca9670e
In bug 1313933, we removed the session store black magic that RDM used to do in
order to hide the container tab.
Unfortunately, that fix appears to have been imperfect. Session store has a
fallback path that can still record the current URL, causing the container URL
to be recorded anyway, even though we asked nicely to please not do that.
In this change, we try a fresh approach of wedging the session history listener
for the container tab so it can't record anything. This avoids the racy
approach that was used before bug 1313933 while still appearing to block the
container URL from being recorded.
MozReview-Commit-ID: JZTYzMAvaEM
--HG--
extra : rebase_source : dff8a35b25994b49f2e31888d49ffcb6b55402bb
By using `LOAD_FLAGS_BYPASS_HISTORY`, we can tell session history explicitly to
ignore the entry for the container UI (which is meant to remain hidden from the
user).
This allows us to remove the horrible racy hack that attempted to have the same
effect.
MozReview-Commit-ID: LnhJpO9UbNI
--HG--
extra : rebase_source : 51c3beeaa4ff081d1f9d3ddd5e00b83c56aa15e1
In bug 1310771, the session store process for gathering data from content was
changed so that the key "historychange" is used instead of "history". Kept the
check for "history" as well, since other places in session store still test for
it.
MozReview-Commit-ID: 4xF7FkxkriI
Minimal support for <a target/> and window.open() which just ensures we at
least open them somewhere (in a new tab). The following things are ignored:
* Specific target names (everything treated as _blank)
* Window features
* window.opener
These things are deferred for now, since content which does depend on them seems
outside the main focus of RDM.
MozReview-Commit-ID: AKEQkKbJicJ
--HG--
extra : rebase_source : 3739f01d7577721096ac67311cbd46fb5964c562
Assist tabbrowser.xml with processing some events such as MozLayerTreeReady
which bubble up from the remote content frame by adding the inner browser to the
WeakMap from browser to tab.
Most likely this should have been in place all along, but a change from bug
1279086 made it more apparent that it was missing because an error is now thrown
when no tab is found for a browser.
MozReview-Commit-ID: 9wYAOcySkN
--HG--
extra : rebase_source : 131b63463d966a7befc1ef736dc2daefcfe4cff9
Bug 1279086 removed setDocShellIsActiveAndForeground and added preserveLayers in
its place. This updates the RDM tunnel to match.
MozReview-Commit-ID: DarZxxTkHVS
--HG--
extra : rebase_source : 7426bf235dd31a0db52a0114c428109f7b262bc8
The primary browser navigational UI should now behave as if it's connected to
the page content in the viewport, including things like:
* Content page's URL is displayed in location bar
* Content page's title is displayed on the tab
* Back / forward navigates the viewport
* Entering a location navigates the viewport
* Page loading progress is displayed in the status bar as usual
MozReview-Commit-ID: FzxWEwj13sJ
