initial query tests
Merge remote-tracking branch 'origin/master' into randy/find-replace-unit-tests
unit test for replace all static text
add test for skip
add test for scroll track markers
Merge remote-tracking branch 'origin/master' into randy/find-replace-unit-tests
Find in Files tests - initial tests
more tests
interim checkin
Finish Find in Files unit tests
better way to wait
Merge remote-tracking branch 'origin/master' into randy/find-replace-unit-tests
more filter tests
revert #7417
rename function
Fix Extension Manager bug: a poorly-scoped jQuery call causes it to see
*all* Bootstrap tabs in the entire DOM as part of its tab set, so it will
crash if any such other tabs exist in the UI.

This was the only jQuery call in the Extension Manager code that wasn't
scoped down to $dlg (or used an equivalent parent selector).
Merge pull request #7328 from adobe/randy/find-replace-unit-tests

Unit Tests for Find, Replace, Find in Files, File Filters
Merge pull request #7559 from adobe/pflynn/ext-manager-jquery-fix

Fix Extension Manager crash when other Bootstrap tabs present in DOM
Merge pull request #7526 from adobe/revert-7417

revert #7417 - visibility:hidden _should_ leave space in the layout, and we already handle display:none properly
Fix #7442: make API consistent between PrefMan and Prefixed PrefMan.

The slightly higher level API provided by PreferencesManager (over the
PreferencesBase.PreferencesSystem) worked nicely but was inconsistent
with the API an extension author gets when they call
`PreferencesManager.getExtensionPrefs`. This change pushes that extra
behavior down into PreferencesBase.PreferencesSystem so that the
APIs are consistent.

This is a non-breaking change that basically adds to the API:

* doNotSave flag for set: calls to `set()` save automatically unless this flag is set. If extension code is already calling `save()`, that means that there will be an extra call to `save()`, but that should have minimal performance impact because `save()` does no saving when the scopes aren't dirty
* support for string contexts: extensions would have to use complete object contexts previously. This adds support for the simpler string contexts and doesn't change the behavior for object contexts.