The `service-worker-child.js` process script is used by actors to control
service workers as needed. This moves it to helper directory near the actors
that make use of it.
MozReview-Commit-ID: LIq1zcU6fBc
--HG--
rename : devtools/server/service-worker-child.js => devtools/server/actors/worker/service-worker-process.js
extra : rebase_source : 8319d60ab2f3ae10d93d063f8932057316325fc3
Move and rename the server's process script (and accompanying JSM) that starts
DevTools for an entire content process from `content-process-debugger-server.js`
to `startup/content-process.js`. `connectToContent` also becomes the more
specific `connectToContentProcess`.
These code paths will likely change more as Site Isolation work continues, but
for now, we have this light cleanup to gather startup-related paths together.
MozReview-Commit-ID: 1evbZMB8T7r
--HG--
rename : devtools/server/content-process-debugger-server.js => devtools/server/startup/content-process.js
rename : devtools/server/content-server.jsm => devtools/server/startup/content-process.jsm
extra : rebase_source : e077dd3dc915ec274f866d53d3539909f8440de1
Move and rename the server's frame script that starts DevTools in remote frames
from `child.js` to `startup/frame.js`. `connectToChild` also becomes the more
generic `connectToFrame`. A few b2g-isms like "app" are also removed.
These code paths will likely change more as Site Isolation work continues, but
for now, we have this light cleanup to gather startup-related paths together.
MozReview-Commit-ID: El8a0OE99gZ
--HG--
rename : devtools/server/child.js => devtools/server/startup/frame.js
rename : devtools/server/tests/mochitest/test_connectToChild.html => devtools/server/tests/mochitest/test_connectToFrame.html
extra : rebase_source : 2735c53587257b215d720204cf7c4581088eba42
On investigation it turns out that no storage types are supported for chrome:// urls.
MozReview-Commit-ID: JZcQg5FvfvN
--HG--
extra : rebase_source : ea3ad83a5b81fb77fedf1ec4707294c45b6a5257
Also change eslint-plugin-mozilla's globals.js to use eslint-scope rather than escope as
ESLint 4.x changed to eslint-scope. This avoids dependency issues that were masked by the
depedencies of eslint-plugin-no-unsanitized's previous version.
MozReview-Commit-ID: 6wLY7Oj0am3
--HG--
extra : rebase_source : 863313d7907e8246d1f5b0ee83164cc0f943f8f6
The path service was created to allow us to track resources that were part of
legacy add-ons, and to map URIs ponting to those resources to add-on IDs, so
that we could apply special behavior to them.
We have better ways to track resources belonging to WebExtensions, so this
code does not benefit them in any significant way.
The only remaining legacy extensions are system add-ons, which we control, and
do not need the path service in order to track.
MozReview-Commit-ID: BKXkcaM7jJx
--HG--
extra : rebase_source : c8cb0f7cec919b767bbcfe5433a6838523747676
- Emit shape change events from highlighter
- Wrap shape highlighter with in-context shape editor singleton
- Link text properties from Rule view into in-context shapes editor
- Write changes to corresponding rule instead of inline style
- Hide shape highlighter on node change or TextProperty disabled/overwritten
- Remove functionality to restore shape editor on refresh
- Refactor and consolidate shape point hover behaviour (still to do: internalize remaining logic for point hover from rules.js and highlighter-overlay.js)
- Update unit tests
MozReview-Commit-ID: JiMTqODgcjU
--HG--
extra : rebase_source : abcaaa220d7cfda839daf77af9b5c01d4444d781
extra : histedit_source : 19060681534b800fc9696cc94f995eca7587ee30
So far, we are drawing the entire line area, and then cutting out the various
margin boxes from each item, in order to show where justify-content applies.
This is dangerous because that means clearing pixels in a canvas where we're
drawing tons of other stuff, and it's easy to accidentally clear unwanted
things.
Instead, now we just draw the justify-content where needed only.
MozReview-Commit-ID: LJN6Fl1by4l
In ContentProcessForward, we listen for console-api-log-event in order
to pass data to the Browser console and Browser toolbox.
But the data is modified and properties are cherry-picked from the original
event, missing some properties probably introduced later like `counter`,
`prefix`, `private`, …
The fix consists in cloning the original event data and only overriding what
needs to be overridden.
MozReview-Commit-ID: 6jSfiRxcHQa
--HG--
extra : rebase_source : 3a4c61c0eb14ccdf584630c508dc439b7718ee45
extra : source : d266983f9cdeba0381f11e00bb6b271ccda561c1
When getting the source for inline scripts in documents, we generally try to use
the cache. However, the toolbox allows you to disable the HTTP cache while open
if you wish.
If the toolbox has disabled the cache, using `fetchFromCache: true` will give
stale data (from the most recent cache-enabled request).
We can avoid stale data here by checking the document's cache state.
MozReview-Commit-ID: J5SJciSyQNj
--HG--
extra : rebase_source : f5fce653f7860b406aa4a580c32e7c15f9cdd0ce
