Bug 1303838 - Switch to existing target tab when clicking links. r=smaug Merge "DOMServiceWorkerFocusClient" & "DOMWebNotificationClicked" to "DOMWindowFocus" event. Utilize the event to switch tab when loading links to an existing target tab. MozReview-Commit-ID: Hd1NkVkrJA1

Bug 1347687 - Skip test if pref gecko.handlerService.defaultHandlersVersion not defined. r=alchen

Backed out changeset a6780188f669 (bug 1314543) for suspicion this cause perma windows 7 xpcshell failures

Bug 1348081 - if we call ProcessPendingQForEntry with considerAll=false we should return if we already found a transaction in the urgent queue. r=mayhemer

Bug 1341572 - Fix multiple HalfOpen socket for a single transaction. r=mcmanus

Backed out changeset 36a2230fbad6 (bug 1347164) for perma failures in own test

Backed out changeset 8af7daaf5f88 (bug 1347164)

Backed out changeset 18c70bc07c6d (bug 1347164)

Backed out changeset bb325d01c421 (bug 1347164)

Bug 1347818 - Part 2. Add documentCharacterSet test. r=masayuki MozReview-Commit-ID: LvUNE7UNpik

Bug 1347818 - Part 1. Clean up documentCharacterSet not to use nsIDOM*. r=masayuki I want to remove nsIDOMNodeList usages from editor excepting old debug code. (BTW, we might have to change to <meta charset> instead of <meta http-equive>, but it should handle by another issue) MozReview-Commit-ID: ArAVOHigKNW

Bug 1343341. Fix a bug with redecoding images whose animation is finished. r=aosmond For animated images with finite animations we can finish running their animation. At which point we won't call RequestRefresh, and so we will never mark the composited frame as valid (since that is the only place we do that). To fix this we mark the composited frame as valid when we finish decoding. But we can do better than that, we can mark the composited frame as valid immediately when we create a new decoded since we are just drawing the final frame from now on.

Bug 1345368 - land NSS 37ccb22f8e51, r=me

Bug 1348111 - Clarify the error message. r=smaug

Bug 1348168 - Disable Mozilla custom ImageBitmap extensions that didn't go through proper API review; r=bzbarsky

Bug 1344892 - Let native calls dispatch to XPCOM event queue; r=snorp Bug 1344892 - 1. Add option to dispatch to priority queue; r=snorp For the regular "gecko" option, change to dispatching to the XPCOM event queue, and add a new "gecko_priority" option that dispatches calls to the widget event queue. GeckoThread.waitOnGecko is changed to wait on both the widget queue and the XPCOM queue. nsAppShell::SyncRunEvent is changed to avoid a possible deadlock condition involving locking sAppShellLock twice. Bug 1344892 - 2. Update dispatchTo = "gecko" options; r=snorp Update some existing dispatchTo = "gecko" options to "gecko_priority", which typically involve UI events or JNI management calls like disposeNative. As a rule, disposeNative is dispatched to the queue with the least priority among the queues that other native members of the same class dispatch to (i.e. "gecko_priority" if all other native members dispatch to "gecko_priority", or "gecko" if any native members dispatch to "gecko"). Bug 1344892 - 3. Update auto-generated bindings; r=me

Bug 1333990: Part 3e - Add tests for content script cache eviction. r=aswan,billm MozReview-Commit-ID: 6SRI8xTuZk5

Bug 1333990: Part 3d - Split observe() method to fix complexity warnings. r=aswan MozReview-Commit-ID: 5ACOf2X5Z7I

Bug 1333990: Part 3c - Evict cached content scripts after a timeout and on memory-pressure. r=aswan,billm This change automatically evicts content scripts 5 minutes after their last use, and flushes the entire cache whenever a memory-pressure event is received. In the case of memory-pressure events other than heap-minimize, we only evict scripts that have been in the cache for longer than 3 seconds (which is a fairly arbitrary number) in order to prevent pre-loads from being evicted and then immediately re-loaded. MozReview-Commit-ID: LCXkI9qVMxS

Bug 1333990: Part 3b - Preload matching content scripts when opening document channels. r=aswan,billm This uses the http-on-opening-request observer that's dispatched in the child process to begin preloading matching content scripts as early in the load cycle as possible. Ideally we would use the network predictor for this, but most of its prediction work happens in the parent process, and there are no simple ways for us to hook into it. This currently does not do any pre-loading in the parent process, mainly because there isn't a good way to distinguish top-level document loads that are happening directly in the parent versus those that are being proxied from the child. MozReview-Commit-ID: dIQW68HtxZ