5402e5e97e2146e59caa74bcc539cf13b52812d5: Bug 1342825 - don't run mochitest browser screenshots on linux64-nightly opt, r=kmoir
Alin Selagea <aselagea@mozilla.com> - Wed, 05 Apr 2017 14:25:49 +0300 - rev 351229
Push 88834 by aselagea@mozilla.com at Wed, 05 Apr 2017 11:26:12 +0000
Bug 1342825 - don't run mochitest browser screenshots on linux64-nightly opt, r=kmoir
9927b6f58b07ccad9c3498180e0ddd4478695855: Bug 1326437 part 3 - Port Ion GetName IC to CacheIR. r=evilpie
Jan de Mooij <jdemooij@mozilla.com> - Wed, 05 Apr 2017 12:22:32 +0200 - rev 351228
Push 88833 by jandemooij@gmail.com at Wed, 05 Apr 2017 10:23:02 +0000
Bug 1326437 part 3 - Port Ion GetName IC to CacheIR. r=evilpie
406065489474d8ff7a70dee8d3923a1b7aded79a: Bug 1326437 part 2 - Don't shape guard non-extensible call objects. r=evilpie
Jan de Mooij <jdemooij@mozilla.com> - Wed, 05 Apr 2017 12:22:29 +0200 - rev 351227
Push 88833 by jandemooij@gmail.com at Wed, 05 Apr 2017 10:23:02 +0000
Bug 1326437 part 2 - Don't shape guard non-extensible call objects. r=evilpie
22813d104a9a3682f3dd8ff7e519e177ac87ec93: Bug 1345398 - Fire WidgetMouseEvent by handling pen generated mouse messages to get Windows native dnd supports. r=jimm
Stone Shih <sshih@mozilla.com> - Mon, 13 Mar 2017 15:40:52 +0800 - rev 351226
Push 88832 by cbook@mozilla.com at Wed, 05 Apr 2017 08:34:41 +0000
Bug 1345398 - Fire WidgetMouseEvent by handling pen generated mouse messages to get Windows native dnd supports. r=jimm Due to Windows doesn't support dnd in the pen message handler, we can't handle and consume WM_POINTER* to fire WidgetMouseEvent. On the other hand, we can't get some pen related attributes from Windows mouse messages. This patch gets and caches the attributes by handling WM_POINTER* but not fire WidgetMouseEvent to support dnd and pen related attributes. When handling the subsequent Windows mouse messages, we use the cached attributes to fire WidgetMouseEvent. Considering we might need to use WM_POINTER* someday, use a preference to control the behavior. MozReview-Commit-ID: 5E60KO1zo0W
dcade1e36862237d950e388441f462bfaa41c0b8: Bug 1193636 - "Use HTTPS for Yahoo! Japan search provider" r=mkaply
dynamis <bugzilla> - Fri, 31 Mar 2017 00:04:00 +0200 - rev 351225
Push 88832 by cbook@mozilla.com at Wed, 05 Apr 2017 08:34:41 +0000
Bug 1193636 - "Use HTTPS for Yahoo! Japan search provider" r=mkaply
a269457f31c9710aa2e338a5c90b954b314c0d0b: Bug 1350933 - Labeling dom/filesystem - part 3 - IPC actors, r=billm
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 05 Apr 2017 09:47:56 +0200 - rev 351224
Push 88831 by amarchesini@mozilla.com at Wed, 05 Apr 2017 07:48:19 +0000
Bug 1350933 - Labeling dom/filesystem - part 3 - IPC actors, r=billm
611184e06d808e4184db57f6030936b83fbf8709: Bug 1350933 - Labeling dom/filesystem - part 2 - DispatchTo{Current,Main}Thread, r=billm
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 05 Apr 2017 09:47:34 +0200 - rev 351223
Push 88831 by amarchesini@mozilla.com at Wed, 05 Apr 2017 07:48:19 +0000
Bug 1350933 - Labeling dom/filesystem - part 2 - DispatchTo{Current,Main}Thread, r=billm
9d0d8e859a640b58f9222ffec4ddd20b69bf9e8e: Bug 1350933 - Labeling dom/filesystem - part 1 - Runnable, r=billm
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 05 Apr 2017 09:47:09 +0200 - rev 351222
Push 88831 by amarchesini@mozilla.com at Wed, 05 Apr 2017 07:48:19 +0000
Bug 1350933 - Labeling dom/filesystem - part 1 - Runnable, r=billm
abdb79a72b8177377404ddbc6d9d06c0ffa8f07c: Bug 1351136 (follow-up) - Fix a harmless argument mis-ordering in a call to profiler_get_start_params(). r=me.
Nicholas Nethercote <nnethercote@mozilla.com> - Wed, 05 Apr 2017 11:56:37 +1000 - rev 351221
Push 88830 by nnethercote@mozilla.com at Wed, 05 Apr 2017 07:10:25 +0000
Bug 1351136 (follow-up) - Fix a harmless argument mis-ordering in a call to profiler_get_start_params(). r=me. Found by Coverity.
72f31ba9e92b20a71a221463719951f9903e2ce4: Bug 1353197 - Add a test for URLSearchParams handling of non-ASCII keys in the record<> ctor, r=annevk
Andrea Marchesini <amarchesini@mozilla.com> - Wed, 05 Apr 2017 08:09:33 +0200 - rev 351220
Push 88829 by amarchesini@mozilla.com at Wed, 05 Apr 2017 06:10:04 +0000
Bug 1353197 - Add a test for URLSearchParams handling of non-ASCII keys in the record<> ctor, r=annevk
975e8f26034796f3bc7b9f0aa18cba4e4e5cf05c: Bug 1346145 - Label nsIDocument::SelectorCache. r=ehsan
Bevis Tseng <btseng@mozilla.com> - Mon, 13 Mar 2017 14:49:28 +0800 - rev 351219
Push 88828 by btseng@mozilla.com at Wed, 05 Apr 2017 05:27:31 +0000
Bug 1346145 - Label nsIDocument::SelectorCache. r=ehsan SelectorCache::NotifyExpired() will be invoked by nsExpirationTracker::TimerCallback() from an unlabel runnable. We adopt the change in nsExpirationTracker to provide a DocGroup EventTarget for the invocation of this callback.
899fd5a47a205adc5ce28ea57e8426a299c79dd3: Bug 1345464 - Add an optional EventTarget to nsExpirationTracker to support Labeling for Quantum-DOM. r=froydnj
Bevis Tseng <btseng@mozilla.com> - Thu, 30 Mar 2017 09:23:36 -0400 - rev 351218
Push 88828 by btseng@mozilla.com at Wed, 05 Apr 2017 05:27:31 +0000
Bug 1345464 - Add an optional EventTarget to nsExpirationTracker to support Labeling for Quantum-DOM. r=froydnj
3ee3add6393dd5923d91328ba47f0a6f55f33f41: Bug 1350177 - Part 3: Refactor SurfaceCache with ExpirationTrackerImpl. r=froydnj,aosmond
Bevis Tseng <btseng@mozilla.com> - Mon, 27 Mar 2017 21:47:23 -0400 - rev 351217
Push 88828 by btseng@mozilla.com at Wed, 05 Apr 2017 05:27:31 +0000
Bug 1350177 - Part 3: Refactor SurfaceCache with ExpirationTrackerImpl. r=froydnj,aosmond Always acquire StaticMutexAutoLock for the use of ExpirationTrackerImpl.
8f496e855383001c787bc218281594abafb7bf2b: Bug 1350177 - Part 2: Fix compiling error after ExpirationTrackerImpl is introduced. r=mystor
Bevis Tseng <btseng@mozilla.com> - Wed, 29 Mar 2017 15:48:47 -0400 - rev 351216
Push 88828 by btseng@mozilla.com at Wed, 05 Apr 2017 05:27:31 +0000
Bug 1350177 - Part 2: Fix compiling error after ExpirationTrackerImpl is introduced. r=mystor
cd56b45db4eb8ce629624a007f2943ea0c8cb632: Bug 1350177 - Part 1: Define ExpirationTrackerImpl as a Thread-Safe Tracker. r=froydnj
Bevis Tseng <btseng@mozilla.com> - Mon, 27 Mar 2017 19:37:29 +0800 - rev 351215
Push 88828 by btseng@mozilla.com at Wed, 05 Apr 2017 05:27:31 +0000
Bug 1350177 - Part 1: Define ExpirationTrackerImpl as a Thread-Safe Tracker. r=froydnj 1. Define ExpirationTrackerImpl which requires AutoLock before calling Tracker APIs. 2. Move expiration logic from nsExpirationTracker to ExpirationTrackerImpl. 3. Keep nsExprationTracker un-thread-safe with fake Lock acquired.
c03d368159cbf653df19416dab2b013eb59b649a: Bug 1346109. Call NotifyApproximateFrameVisibilityUpdate after we set a display port base rect. r=botond
Timothy Nikkel <tnikkel@gmail.com> - Wed, 05 Apr 2017 00:18:11 -0500 - rev 351214
Push 88827 by tnikkel@gmail.com at Wed, 05 Apr 2017 05:18:22 +0000
Bug 1346109. Call NotifyApproximateFrameVisibilityUpdate after we set a display port base rect. r=botond NotifyApproximateFrameVisibilityUpdate gets the displayport so we want the base rect set before calling it. We also don't want to record the displayport if we ignored it in the actual visibility pass.
19c4e80bee84eb2515f71df3649423245d0c13d5: Bug 1353181 followup - Fix non-DEBUG warnings-as-errors bustage.
L. David Baron <dbaron@dbaron.org> - Tue, 04 Apr 2017 21:42:18 -0700 - rev 351213
Push 88826 by dbaron@mozilla.com at Wed, 05 Apr 2017 04:42:40 +0000
Bug 1353181 followup - Fix non-DEBUG warnings-as-errors bustage.
63a14b2f3c7432bc2898a5f814a6ad84539cd8ad: Bug 1353187 - Guard access to the frame property table with a frame state bit. r=dholbert
L. David Baron <dbaron@dbaron.org> - Tue, 04 Apr 2017 20:59:21 -0700 - rev 351212
Push 88825 by dbaron@mozilla.com at Wed, 05 Apr 2017 04:14:17 +0000
Bug 1353187 - Guard access to the frame property table with a frame state bit. r=dholbert This protects all accesses to the frame property table with a bit stored on the frame. This means we avoid hashtable operations when asking about frame properties on frames that have no properties. The changes to RestyleManager, and the new HasSkippingBitCheck API, are needed because RestyleManager depended on being able to ask for properties on a deleted frame (knowing that the property in question could not have been set on any new frames since the deleted frame was destroyed), in order to use the destruction of the properties that happens at frame destruction as a mechanism for learning that the frame was destroyed. The changes there preserve the use of that mechanism, although it becomes a bit uglier. The ugliness is well-deserved. MozReview-Commit-ID: BScmDUlWq65
c3075684667085325129a6ae7fb0375e476b9036: Bug 1353187 - Give frame properties the const-ness semantics of member variables. r=dholbert
L. David Baron <dbaron@dbaron.org> - Tue, 04 Apr 2017 20:59:21 -0700 - rev 351211
Push 88825 by dbaron@mozilla.com at Wed, 05 Apr 2017 04:14:17 +0000
Bug 1353187 - Give frame properties the const-ness semantics of member variables. r=dholbert This makes it so that, given a |const nsIFrame*|, a caller can retrieve properties but not set or remove them, but with an |nsIFrame*| all operations are allowed. I believe this is sensible since properties act as extended member variables for things that are needed rarely, and these are the const-ness semantics of member variables. This also avoids the need for const_cast<nsIFrame*> to cast away const in the following patch, which guards property access with a frame state bit. MozReview-Commit-ID: IJ9JnGzdH51
e4ac2148c9204c4a61f572b947a9e998b83ccfc9: Bug 1352888 - Don't set the collision flag when adding to PLDHashTable if we've already found the entry we're going to add. r=njn
L. David Baron <dbaron@dbaron.org> - Tue, 04 Apr 2017 20:59:21 -0700 - rev 351210
Push 88825 by dbaron@mozilla.com at Wed, 05 Apr 2017 04:14:17 +0000
Bug 1352888 - Don't set the collision flag when adding to PLDHashTable if we've already found the entry we're going to add. r=njn PLDHashTable's entry store has two types of unoccupied entries: free entries and removed entries. The search of a chain of entries (determined by the hash value) in the entry store to search for an entry can stop at free entries, but it continues across removed entries, because removed entries are entries that may have been skipped over when we were adding the value we're searching for to the hash, but have since been removed. For live entries, we also maintain this distinction by using one bit of storage for a collision flag, which notes that if the hashtable entry is removed, its place in the entry store must become a removed entry rather than a free entry. When we add a new entry to the table, Add's semantics require that we return an existing entry if there is one, and only create a new entry if no existing entry exists. (Bug 1352198 suggests the possibility of a faster alternative Add API where the caller guarantees that the key is not already in the hashtable.) When we search for the existing entry, we must thus continue the search across removed entries, even though we record the first removed entry found to return if the search for an existing entry fails. The existing code adds the collision flag through the entire table search during an Add. This patch changes that behavior so that we only add the collision flag prior to finding the first removed entry. Adding it after we find the first removed entry is unnecessary, since we are not making that entry part of a path to a new entry. If it is part of a path to an existing entry, it will already have the collision flag set. This patch effectively puts an if (!firstRemoved) around the else branch of the if (MOZ_UNLIKELY(EntryIsRemoved(entry))), and then refactors that condition outwards since it is now around the contents of both the if and else branches. MozReview-Commit-ID: CsXnMYttHVy
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip