This is currently a no-op, but the idea here is to make sure to set the
process to "active" when we're about to use it for something.
MozReview-Commit-ID: 2QUlALhfD4k
--HG--
extra : rebase_source : 13a67e9353bb47593b1394ce7ae7a7b6eef6e381
By showing users an upsell, positioned as a feature, as part of the save confirmation and make it easy for users to get the mobile app, more users will understand the value of the Pocket mobile and start using the mobile app.
The initial experiment will target existing logged in English users only.
We've added flags to the server response on the save request that:
- Set whether the user has the mobile app
- Which variant of the experiment the user should be enrolled in
If the user has an account, but they've never installed the Android or iOS app, we will display a new button inline in the current panel that will email a link to the mobile application to the user.
MozReview-Commit-ID: 2xtPv5GPVbL
***
Bug 1451840 - Add button to Pocket doorhanger to request mobile app
- Specified default color on buttons
- Removed unnecessary css styles
- Resized icon display size
- Made RTL friendly
- Simplified SVGs
- Updated buttons to be html buttons for screen readers
MozReview-Commit-ID: HdTi1CZbXdc
--HG--
extra : rebase_source : ac259ac308d7a08dcbddb43b9420f7f997f57e23
This allows keyboard shortcuts to work right away when the input field
isn't present.
MozReview-Commit-ID: COmmybkUu0m
--HG--
extra : rebase_source : 1e40fc7be3e97b990b1b3839482618eb9b7f166b
This patch implements Drop operation on Wayland/Gtk+. That's because drop operations are part
of clipboard on Wayland and we use our own paste clipboard handler on Wayland (Bug 1282015).
Wayland drop data are provided by wl_data_device_listener, it provides us drag and drop callbacks
which we route to nsDragService module.
MozReview-Commit-ID: 9uGYPg9YF6P
--HG--
extra : rebase_source : 613c079960d5d8522609374ce7e9ad23d5908f3f
Instead of downloading the build artifacts (rather hackily) in moztest.fixtures, this now happens
directly in the taskgraph module via the run-task script.
For now extraction and setup happens in the task's command key. It might be a good idea to figure
out a syntax to tell run-task to do this extraction, e.g something like:
run:
using-artifacts:
build:
target.tar.bz2:
extract: true
path: /home/worker/build
name: firefox
But for now I wanted to avoid this extra complexity, so maybe it could be done in a follow-up.
MozReview-Commit-ID: KOhFFpFdP7Y
--HG--
extra : rebase_source : dcea36661fa9c6442c76c850ccc67f8f6d924fda
This adds a 'use-artifacts' key to the run_task schema. Tasks can specify artifacts to download like this:
run:
using: run-task
use_artifacts:
build:
- target.tar.bz2
- target.common.tests.zip
- target.mochitest.tests.zip
This will cause the run-task script to download those three artifacts from the task's 'build' dependency.
If the task doesn't have a 'build' dependency, taskgraph generation will error. The artifacts will be
downloaded into $USE_ARTIFACT_PATH. It is up to the task to do whatever extracting/setup may be required.
E.g this setup could go in the task's command.
At this time, only 'run-task' tasks using docker-worker are supported.
MozReview-Commit-ID: 3f02oCys62i
--HG--
extra : rebase_source : e8a85040e45042b537d4119334c4a8b7280b295c
There was a race between the fetching of the object properties and the
expansion of the stacktrace of the console.error message. In the end, the
message was re-rendered, without the object being expanded.
To prevent such thing, we stop the propagation of the click on the Tree
node. Here the fix is done directly in the Reps bundle so it can be applied
on beta, without unrelated code changes we'd have if doing a full bundle release.
The fix will be backported to the Tree components so it's included in the
bundle on the next reps release.
A test is added to make sure we don't regress this.
MozReview-Commit-ID: Di8YxJ7P1Wl
--HG--
extra : rebase_source : be63fb2764ed97864bfe4cccf03d336df46de4db
The fix was made in Reps, in Bug 1452566, so we add a
test to make sure we don't regress.
MozReview-Commit-ID: EddzoHVs4Yo
--HG--
extra : rebase_source : ef73bd54d844c1cf286b5fa07a3b380ac2707281
Fix the ownership check to correctly check if we're cutting or copying.
MozReview-Commit-ID: 1eLt4Fyy2nE
--HG--
extra : rebase_source : 78850cde9d4433d844bef32b6624331460663025
The patch handles timeLog packets we receive from the backend.
We add some stubs in order to have access to packets in mocha,
and some mocha tests to make sure we render those messages as expected,
be it when the timer exists or not.
The BASE_PATH constant now makes use of MOZ_DEVELOPER_REPO_DIR environment
variable in order to have an absolute path; without it the stubs couldn't
be written to local files.
MozReview-Commit-ID: Fx4DyRgOzcd
--HG--
extra : rebase_source : 8b9b40cc6aa6264123b231f7c2fe97dc56a41895