This was done automatically replacing:
s/mozilla::Move/std::move/
s/ Move(/ std::move(/
s/(Move(/(std::move(/
Removing the 'using mozilla::Move;' lines.
And then with a few manual fixups, see the bug for the split series..
MozReview-Commit-ID: Jxze3adipUh
This is disabled already in updater-common.build and similar places, so that
they can use UniquePtr and include <new>.
These files were getting around it because they didn't include the stl at all,
but now they include <utility> transitively for std::move.
MozReview-Commit-ID: IaU9mRbbCAk
Implemented Rust/C++ glue code for rtcp-fb
Implemented parsing support for rtcpfb-wildcard in rust
Activated c++ unit tests
MozReview-Commit-ID: 5xRSQz7pucZ
--HG--
extra : rebase_source : 97fdfda9134197381d16e0a61dda5357bba9e9da
Some of the RDM toolbar icons relied on `background-size: cover` from the
overall DevTools button styles, which was removed recently in bug 1442531. We
restore RDM's appearance by copying this style into RDM styles.
MozReview-Commit-ID: KcZwaRgZUsh
--HG--
extra : rebase_source : 4a2f548f6f073870ad06183a33bdaabc2bff6d92
This patch will apply the grid layout to the toolbar.
If devtools's width is narrow, we expected that devtool display chevron and the
controls elements only(i.e. chevron and meatball and close button).
In order to display these button, a wrapper of toolbar will use grid layout.
Basically, this patch define grid columns as follow:
------------------------------------------------
| Picker | tooltabs | commands | controls |
| auto | 26px ~ 1fr | auto | max-content|
------------------------------------------------
We can disable the picker and command buttons, in this case, a toolbar will
stretch the tooltabs width by using grid-column-start/end.
MozReview-Commit-ID: ByY2qt2xhAg
--HG--
extra : rebase_source : c86b30acbfc32172eceea365e84ed03d717d5345
This patch will allow that all buttons which accessing the tool panel is
overflowed. i.e. toolbar will display chevron button only.
MozReview-Commit-ID: GbKbAhtpYt7
--HG--
extra : rebase_source : 971aef121c329e6a5ba3ada24015a1d820aab26a
This patch will two impprove performances:
* Remove unnecesarry reflow by using the DOMWindowUtils.getBoundsWithoutFlushing().
This is a tiny performance improvement. Previous code will reflow on each
tab width caclculation.
* Change requestIdleCallback's timeout to 100ms.
If user resize the devtool's width over time, overflow calculation will occur
every 300ms. This patch will reduce this delay.
MozReview-Commit-ID: FxZuK0wGxHk
--HG--
extra : rebase_source : 06a0a4ba5312125e7d15378c253f7278a39a69f9
If we're running on Valgrind, we'll be making forward progress at a rate of
somewhere between 1/25th and 1/50th of normal. This can cause shutdown
timeouts frequently enough to be a problem for the Valgrind runs on
automation. As an attempt to avoid the worst of this, this patch scales up
the presented timeout by a factor of three. For a non-Valgrind-enabled
build, or for an enabled build which isn't running on Valgrind, the timeout
is unchanged.
--HG--
extra : rebase_source : 7c2c51f65137805a34ededc241eb04708fae15a6
While some builds have a PERFHERDER_EXTRA_OPTIONS environment set on the
taskcluster side, many others have the equivalent set at the mozharness
level. But only the former are actually linted against, which,
unsurprisingly, translates to conflicting values between some of the
mozharness configs.
So we move those configurations to taskcluster, enable the lint on all
the kinds that look like builds (based on them using the build_attrs
transform), and adjust the values to stop conflicting. Notably, for
searchfox and static-analysis-autotest.
--HG--
extra : rebase_source : 097333608e61e1df66e5d8f914e15784f35e58f2
Have the home preferences page notify when it loads instead of relying on findInPage to trigger sync pane to init.
MozReview-Commit-ID: EJlJDfYBHFO
--HG--
extra : rebase_source : ae5104ec18aefca9241be1b61072b786fa9e6815
Just a cleanup patch, this function would be cleaner without the
nesting.
MozReview-Commit-ID: DD48E2HSQOL
--HG--
extra : rebase_source : 79cf6b3eee00149fa5993c10bd69649633307fee
extra : histedit_source : 1fde6b0291acddcf73569b2e43757030c38d9e69
Add ACTIVE_DOCGROUPS_PER_TABGROUP and TOTAL_DOCGROUPS_PER_TABGROUP to
collect data on how many docgroups a tabgroup has whenever a top level
content document associated with that tabgroup would hide. This gives
a fairly accurate estimate of the number of docgroups a site
uses. TOTAL_* counts all docgroups while ACTIVE_* only count docgroups
with at least one document not in the bfcache.