TSFTextStore shouldn't notify TSF of selection change until MaybeFlushPendingNotifications() is called and there is no cached content because while there is cached content, neither TSF nor TIP may allow to change selection by web applications. Therefore, ITextStoreACP::GetSelection() and similar methods need to use mSelection instead of actual selection in the focused editor. Therefore, TSFTextStore should store selection change data during keeping storing content cache and notify it when the cache is cleared. So, when TSFTextStore notifies TSF of selection change, TSFTextStore needs to update mSelection to the actual selection which is stored in mPendingSelectionChangeData.
MozReview-Commit-ID: 8ZWASzu7Znv
--HG--
extra : rebase_source : 0bfaef0bbffd72d661c84992cc8c842215e3407a
This patch stop clearing mContentForTSF at unlocking the document because we should keep it until active composition is committed. If so, TSF/TIP won't be confused by content changes by JS. So, this is important for a11y of TIP users in some complicated websites like GoogleDocs, Facebook, etc.
Note that this patch doesn't work well without following patches. We need to stop notifying TSF of selection changes and text changed while mContentForTSF is valid.
MozReview-Commit-ID: 9QOGZxdYU3I
--HG--
extra : rebase_source : 19a6eeb2357825643497caf5a5298c55f08a0670
- GLScreenBuffer::CreateFactory has been overloaded to accept either
a CompositableForwarder or a ClientIPCAllocator.
- WebVR 1.0 API implementation in Bug 1250244 uses GLScreenBuffer
without a CompositableForwarder.
MozReview-Commit-ID: GWR1XuIgPBT
--HG--
extra : rebase_source : 5a8d058b6f08345eb431b1a6d39bdce3882487ee
Firefox-ui functional tests which use local test data should report with the Tier-1 level.
Due to restrictions of Tier-1 the other tests with remote test data have to be kept as Tier-2 jobs.
The patches reorganize our hierarchy of templates accordingly.
MozReview-Commit-ID: 9QcuYUzkvwf
--HG--
extra : rebase_source : de0b2437fe047aa2e502d16ae477cd2f3b5b21f7
There are two subsets of functional tests which use local or remote test data.
The appropriate subset can be selected via the --tag option which comes from Marionette.
MozReview-Commit-ID: Bfu6IsXVc2T
--HG--
extra : rebase_source : 7b09a0bc586277210647993c3563d71330af63d1
Firefox-ui functional tests which use local test data should report with the Tier-1 level.
Due to restrictions of Tier-1 the other tests with remote test data have to be kept as Tier-2 jobs.
The patches reorganize our hierarchy of templates accordingly.
MozReview-Commit-ID: 9QcuYUzkvwf
--HG--
extra : rebase_source : 0756bbd2f79d4a8feb4ff093efa1b84fe52a2d5a
There are two subsets of functional tests which use local or remote test data.
The appropriate subset can be selected via the --tag option which comes from Marionette.
MozReview-Commit-ID: Bfu6IsXVc2T
--HG--
extra : rebase_source : 43069f038bfb1427253684af896bcacb2cb6992c
This change allows Marionette harness to work with the Nightly which
no longer has the `device` capability. It was removed in Bug 1282800.
MozReview-Commit-ID: BIW7cVvHhp0
--HG--
extra : rebase_source : 5e4fd5653dce409b8f4eacfead3715064ae10fd9
This will only run if they receive a WGL context, and we have a blocklist
entry for this. Since there isn't a reason right now to want WGL without
DXGL, we should tie these together.
MozReview-Commit-ID: ymtVT5dJIZ
