This patch is generated by the following sed script:
find . ! -wholename '*/.hg*' -type f \( -iname '*.html' -o -iname '*.xhtml' -o -iname '*.xul' -o -iname '*.js' \) -exec sed -i -e 's/\(\(text\|application\)\/javascript\);version=1.[0-9]/\1/g' {} \;
MozReview-Commit-ID: AzhtdwJwVNg
--HG--
extra : rebase_source : e8f90249454c0779d926f87777f457352961748d
The action creator for removing custom devices calls the one for remove device
association directly, which skips the step of also messaging the manager.
I've made the simplest change to fix just this issue, which moves the message
sending into the action creator for this one case. Bug 1332754 will apply the
same approach to other messages (they aren't causing issues yet since they are
not called from other action creators in the same way).
MozReview-Commit-ID: AICcT2vG1wl
--HG--
extra : rebase_source : 3c6c6f28cfe0fc96a429b3167e2d6ee79810cf25
This gets closer to Helen's mockup. The spacing is a bit tight. When adjusting
the modal size, I used the most popular DevTools screen resolution (1366 x 768)
as a reference.
MozReview-Commit-ID: 4EjJKKhuxpA
--HG--
extra : rebase_source : 01d293e177d38548df2997db6aed5d822c6e1101
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
If a device is active, remove it on resize. If not, leave device properties
alone, so that things like touch simulation stay enabled when resizing without
a device.
MozReview-Commit-ID: Hvo6AdTJRBJ
--HG--
extra : rebase_source : d8c49b55c01ca625b7e85c52c4be63175ba98fd0
Use "change" instead of "update" terminology with viewport properties.
Remove redundant "viewport" word from viewport changes.
MozReview-Commit-ID: HSFLiZyTVYy
--HG--
rename : devtools/client/responsive.html/test/unit/test_change_viewport_device.js => devtools/client/responsive.html/test/unit/test_change_device.js
extra : rebase_source : ddf227119edc0e022d586cf46b448e1891d059aa
When starting and stopping RDM, we need want to ensure tab listener state flags
are preserved for the tab involved, which is a bit tricky with the tab dance
RDM is doing.
The state flags ensure the browser will call the correct handlers when switching
tabs to update the primary browser UI. For example, this is needed to correctly
update the enabled state of the view source command for the current tab.
MozReview-Commit-ID: 7lKY0DKxgJH
--HG--
extra : rebase_source : 5cc2deafc31f8f58d13d78e5b2524d60897bf5b9
In bug 1318767, `updateBrowserRemoteness` was changed to take the `remoteType`
as part of an options argument, but the RDM call site wasn't updated.
MozReview-Commit-ID: 8GSSwicaHvz
--HG--
extra : rebase_source : 6c945bc74c5b4a366c461f34566db1dfc2eb0435
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
