This test uses a Document with a fixed-width meta viewport. This test
simulates resizing the RDM pane from a wide landscape size to a small
square size, and back again. It does this again with meta viewport
support turned on.
Differential Revision: https://phabricator.services.mozilla.com/D22438
--HG--
extra : source : 2fa518cb0dfc656c6f0c5d5dfbad38348be6f31f
There are two viewports: the layout (or content) viewport, and the visual
viewport. This change ensures that we are both setting and checking the
visual viewport size, which is the size shown in the RDM control bar.
It is still possible to get the layout viewport with getContentSize().
Differential Revision: https://phabricator.services.mozilla.com/D22437
--HG--
extra : source : afaf26d7df4235daef3157d74b3bcd69761c6393
This test uses a Document with a fixed-width meta viewport. This test
simulates resizing the RDM pane from a wide landscape size to a small
square size, and back again. It does this again with meta viewport
support turned on.
Differential Revision: https://phabricator.services.mozilla.com/D22438
--HG--
extra : moz-landing-system : lando
There are two viewports: the layout (or content) viewport, and the visual
viewport. This change ensures that we are both setting and checking the
visual viewport size, which is the size shown in the RDM control bar.
It is still possible to get the layout viewport with getContentSize().
Differential Revision: https://phabricator.services.mozilla.com/D22437
--HG--
extra : moz-landing-system : lando
This makes it possible to copy paste the number of times the message is repeated
Differential Revision: https://phabricator.services.mozilla.com/D23667
--HG--
extra : moz-landing-system : lando
This prop will add a classname in the NotificationBox element, that we then style to make the text wrap
Differential Revision: https://phabricator.services.mozilla.com/D23455
--HG--
extra : moz-landing-system : lando
This replaces https://phabricator.services.mozilla.com/D23701, which couldn't be autoland-ed due to merge conflict, but my local gecko-dev wouldn't work properly, so I needed to start from scratch.
This has been submitted via mercurial.
Differential Revision: https://phabricator.services.mozilla.com/D23767
--HG--
rename : devtools/client/debugger/new/src/components/Editor/ColumnBreakpoints.css => devtools/client/debugger/new/src/components/Editor/Breakpoints.css
extra : moz-landing-system : lando
TODO: Don't use the alias function and import getBreakpointsList from all used locations (many)
Differential Revision: https://phabricator.services.mozilla.com/D23600
--HG--
extra : moz-landing-system : lando
Added disconnect from device funtion + button to be displayed in runtime page when device is connected
Differential Revision: https://phabricator.services.mozilla.com/D18588
--HG--
extra : moz-landing-system : lando
Depending on the load, this.jsterm might not be
set when switching to the console panel, and can
cause a crash (blank tab).
This patch checks that this.jsterm exists before
taking further actions.
Differential Revision: https://phabricator.services.mozilla.com/D23511
--HG--
extra : moz-landing-system : lando
Summary:
Returning null here leaves us in an infinite loading state because null is treated as neither
success nor failure.
Reviewers: jlast
Bug #: 1534847
Differential Revision: https://phabricator.services.mozilla.com/D23453
Summary:
If users navigate while source text is loading, we need to ignore existing
cached promises because they may resolve and then not actually set the
resulting source, because the source was deleted from the source list.
We want to explicitly use a new cache entry if we have navigated.
Reviewers: jlast
Bug #: 1534847
Differential Revision: https://phabricator.services.mozilla.com/D23452
Summary:
Splitting up this logic makes us less likely to introduce code that would break
the caching behavior. If you look closely at these changes, you'll notice that
there actually one one early return in this code that would cause us to
exit without clearing the 'requests' cache meaning we could get stuck in
an infinite loading state.
Reviewers: jlast
Reviewed By: jlast
Bug #: 1534847
Differential Revision: https://phabricator.services.mozilla.com/D23451
The position of remote browser was not updated by resizing the window and
changing the align of viewport etc, although will be updated when the window
moves, the frame reflows and so on.
Thus, in this patch, update the position of remote browser before showing
context menu so as to locates at proper position.
I investigated though, when reflow and moving happens, the position is updated
by TabParent::UpdateDimensions()[1]. This patch as well is taking an approach
which update the position explicitly by TabParent::UpdateDimensions() before
showing context menu.
[1] https://searchfox.org/mozilla-central/source/dom/ipc/TabParent.cpp#729
Differential Revision: https://phabricator.services.mozilla.com/D23470
--HG--
extra : moz-landing-system : lando
