This leaves getAdjustedQuads alone because it lives in its own world and its
result gets sent over IPC. That leaves things in a bit of an intermediate
state, but that should be OK for now.
MozReview-Commit-ID: DH6eGqCFhPr
--HG--
extra : rebase_source : 39feed5868c86a104e586f40bd1e80e8f8f34e0b
For CSS files which were used via both chrome:// and resource://, I converted
all usages to resource:// and removed the chrome:// copy to reduce file
duplication.
I believe most DevTools CSS could be using resource:// throughout, but that's
left as follow up work for now.
MozReview-Commit-ID: G7oxZqjodwv
--HG--
extra : rebase_source : d6ae487f35cdeddd32aa96d95d62113ba0565b2a
Most test modifications deal with listening to the proper events.
As mentioned in the parent commit, the keyboard navigation for the
inspector-search changed a bit with this change, so the related test
case is using a slightly different scenario.
MozReview-Commit-ID: BgSa69bSSFB
--HG--
extra : rebase_source : a1b565f6b54f2c8e3d641794aaa6aa43a2c75134
Fixed regression from Bug 1168246 and added a unit test to loosely check that
the autocomplete popup moves along with autocompleted query.
MozReview-Commit-ID: H7t5WjkwBE4
--HG--
extra : rebase_source : d876338475ee1b1ae7ef30a9da8bea24c775c948