60f1a8471c7453bcc3b2dce64bc05881bb8f1ae3: Bug 1453148: Let overflow parse two values. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 10 Apr 2018 18:40:22 +0200 - rev 780952
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
Bug 1453148: Let overflow parse two values. r?xidorn Per https://github.com/w3c/csswg-drafts/issues/2484. MozReview-Commit-ID: D7M3PhnTtD2
d194a40ad5bc0a0e6f7b47d121eab99fac2893cd: Revert "WIP get rid of nsStyleImageRequest." draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 10 Apr 2018 15:15:50 +0200 - rev 780951
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
Revert "WIP get rid of nsStyleImageRequest." This reverts commit 4408bc2eafa196d478e2ce2376412e76aeb2fe79.
904f8fb3aaaf88d9f3e191dc34510ef3b34fedc8: WIP get rid of nsStyleImageRequest. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 10 Apr 2018 15:15:28 +0200 - rev 780950
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
WIP get rid of nsStyleImageRequest. MozReview-Commit-ID: CsXQ3vqcM65
3182c4cf0b3878e3148579961d1e0389f9b865dc: Bug 1452889: Assert more tightly. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 10 Apr 2018 11:21:22 +0200 - rev 780949
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
Bug 1452889: Assert more tightly. r?bz Let's see if listboxes are the only ones breaking invariants. MozReview-Commit-ID: DSgfEoCOI78
a04f04708f5e9d1fd5f0fcca4bf843ecc0b48c5a: Bug 1452889: Handle appending multiple items to a listbox correctly. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 10 Apr 2018 11:15:39 +0200 - rev 780948
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
Bug 1452889: Handle appending multiple items to a listbox correctly. r?bz What happened in bug 1446368 is the following: We append two items to an empty listbox. We can't construct lazily because this is XUL, so that goes through IssueSingleInsertNotifications for each of both. When we insert the first one we call LazilyStyleNewChildRange _only on the first sibling_, yet the listbox code tries to construct frames for the next sibling too from CreateRows, yet the next sibling is unstyled, so we panic. Instead of handling it in ContentRangeInserted but not ContentAppended, just do it in the listbox-specific code instead, which looks slightly cleaner (though we can't assert we're constructing async). This should fix the case where the listbox is display: none or what not which, combined with the patch in bug 1303605, supersede the backed out patch in bug 1429088, which was backed out because listboxes suck. MozReview-Commit-ID: D7UQ41S6Ras
e011e134d4a0792dbf7d9c5b2f3da1ae6b64fc3d: Bug 1446368 - Remove the XUL tree from siteDataRemoveSelected. r=paolo draft
Johann Hofmann <jhofmann@mozilla.com> - Fri, 06 Apr 2018 12:59:03 +0200 - rev 780947
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
Bug 1446368 - Remove the XUL tree from siteDataRemoveSelected. r=paolo MozReview-Commit-ID: 3mPP8fhxowE
9558a7b351301d089f4ecbd2e485a0288c832ba9: Bug 509958: Unprefix :-moz-selection. r?dbaron,xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 25 Mar 2018 17:31:55 +0200 - rev 780946
Push 106163 by bmo:emilio@crisal.io at Thu, 12 Apr 2018 09:00:35 +0000
Bug 509958: Unprefix :-moz-selection. r?dbaron,xidorn Our implementation is totally not what the spec says, but totally what other UAs do, see https://github.com/w3c/csswg-drafts/issues/2474. So given this is causing webcompat pain, I think we should be pragmatic and just unprefix this. We could keep serialization and getComputedStyle with ::selection working with a bit more effort, like we do for :-moz-placeholder, but I'd prefer not doing at least the serialization bit, and just alias in nsCSSPseudoElements :-moz-selection to selection too. MozReview-Commit-ID: 6lxctozRDqv
1203a93a97f69a95cdd717c0e672f4ff5cda53a0: Bug 1363168 - Add support for OSX Share feature. r=gijs, r=mstange draft
Dale Harvey <dale@arandomurl.com> - Mon, 12 Mar 2018 09:16:51 +0000 - rev 780945
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1363168 - Add support for OSX Share feature. r=gijs, r=mstange MozReview-Commit-ID: sJXl2If9Ou
23168b46da1ea05b0fe3574eba9e9286ad346ac2: Bug 1452930 - Incorrect sizing of the search plugin icon. r=florian
Paolo Amadini <paolo.mozmail@amadzone.org> - Tue, 10 Apr 2018 15:30:59 +0100 - rev 780944
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1452930 - Incorrect sizing of the search plugin icon. r=florian MozReview-Commit-ID: 3iAtuqa0N7U
69f03ba7f76178f01fa572385284f93946f380d6: Bug 1449833 - Use StaticPrefs in nsJSEnvironment.cpp. r=sfink
Nicholas Nethercote <nnethercote@mozilla.com> - Tue, 27 Mar 2018 13:26:38 +1100 - rev 780943
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1449833 - Use StaticPrefs in nsJSEnvironment.cpp. r=sfink MozReview-Commit-ID: GELa2l1ZonV
7c1ce0dd15f1e2b3987465b721906db1a479523b: Bug 1453015 - nsBufferedInputStream::Available must return NS_OK until its buffer contains data, r=mayhemer
Andrea Marchesini <amarchesini@mozilla.com> - Thu, 12 Apr 2018 07:27:54 +0200 - rev 780942
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1453015 - nsBufferedInputStream::Available must return NS_OK until its buffer contains data, r=mayhemer If the underlying stream returns an error, this should not be propagated until the internal buffer is not empty.
1e9190687c32a0fba7c3c5d2ad2b8ec2f1da2e8e: Bug 1449100 - Move network details panel toggle buton next to the sidebar tabs. r=Honza
Gabriel Luong <gabriel.luong@gmail.com> - Wed, 11 Apr 2018 11:22:24 -0400 - rev 780941
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1449100 - Move network details panel toggle buton next to the sidebar tabs. r=Honza
62ec6e74f1e13b98f38aa2b4d7d5209101877756: Bug 1431071 - Grid line names suggestions offered in inspector autocomplete if element is in a grid and rule applies. r=gl, jdescottes
Erica Wright <ewright@mozilla.com> - Wed, 04 Apr 2018 14:01:19 -0400 - rev 780940
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1431071 - Grid line names suggestions offered in inspector autocomplete if element is in a grid and rule applies. r=gl, jdescottes MozReview-Commit-ID: HGINxducS4x
e6fddf976820916bc5f6a71d85a2c7637ba3cfb7: Bug 1453053 part 4. Remove the QI implementation from ChildProcessMessageManager, ChromeMessageBroadcaster, ChromeMessageSender, ContentFrameMessageManager, ContentProcessMessageManager. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:25 -0400 - rev 780939
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1453053 part 4. Remove the QI implementation from ChildProcessMessageManager, ChromeMessageBroadcaster, ChromeMessageSender, ContentFrameMessageManager, ContentProcessMessageManager. r=qdot ChildProcessMessageManager, ChromeMessageBroadcaster, and ChromeMessageSender only implement nsIMessageSender and nsIContentFrameMessageManager. Neither one has QIs in JS now. ContentFrameMessageManager only implements nsIDOMEventTarget, which there are no JS QIs for. ContentProcessMessageManager implements nsIMessageSender and nsISupportsWeakReference. The only JS QI for nsISupportsWeakReference is definitely not happening on this object. MozReview-Commit-ID: 67dxaQlhpGc
216327b1d4b418fa017ffeed069d1ed22ebc7b32: Bug 1453053 part 3. Remove JS QIs to nsIMessageSender. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:25 -0400 - rev 780938
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1453053 part 3. Remove JS QIs to nsIMessageSender. r=qdot MozReview-Commit-ID: 4TS38gebl7l
4b2e0e54b9301a779838c9989a9ee5569b348c02: Bug 1453053 part 2. Remove the QI implementation from Attr, Comment, DocumentType, ProcessingInstruction, Text. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:25 -0400 - rev 780937
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1453053 part 2. Remove the QI implementation from Attr, Comment, DocumentType, ProcessingInstruction, Text. r=qdot All of these have implementations that only QI to nsIDOMNode and nsISupports, and no one QIs things to nsIDOMNode in script anymore. MozReview-Commit-ID: 2L4VCEEsLkS
f57ccba9c9b51bf5bb1c01517c8af1f5f3ebe099: Bug 1453053 part 1. Remove useless QIs to nsIDOMNode. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:25 -0400 - rev 780936
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1453053 part 1. Remove useless QIs to nsIDOMNode. r=qdot MozReview-Commit-ID: GokPD2buxzN
3406e123d279f0959468a4de10e8983cc3d327dc: Bug 1452786 part 2. Stop using a generated chromeonly isInstance method. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:07 -0400 - rev 780935
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1452786 part 2. Stop using a generated chromeonly isInstance method. r=qdot This changes semantics in all sorts of ways (e.g. now we get the right proto from our |this| value instead of it being baked into the function). But if all our chrome callers are well-behaved this should be ok. We _could_ bake the proto id and depth into the function itself by using js::NewFunctionWithReserved if it were not for Xrays. Those already need the reserved slots on functions we Xray. MozReview-Commit-ID: 1bYrKWWIc1P
f87a1de08a8ac787d53034c1f36a13946f22b8a4: Bug 1452786 part 1. Move the "is chrome" check for installing [ChromeOnly] stuff into the shared CreateInterfaceObjects method. r=qdot
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:05 -0400 - rev 780934
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1452786 part 1. Move the "is chrome" check for installing [ChromeOnly] stuff into the shared CreateInterfaceObjects method. r=qdot Right now we do this check pretty much always anyway for isInstance... we do it twice for anything that actually has [ChromeOnly] bits. MozReview-Commit-ID: FHbYED4FPJe
03a535f247d807f960caf507938fa9c16c967160: Bug 1453487 part 3. Make nsIDOMEventListener noscript. r=smaug
Boris Zbarsky <bzbarsky@mit.edu> - Thu, 12 Apr 2018 00:06:00 -0400 - rev 780933
Push 106162 by bmo:dharvey@mozilla.com at Thu, 12 Apr 2018 08:44:05 +0000
Bug 1453487 part 3. Make nsIDOMEventListener noscript. r=smaug MozReview-Commit-ID: 9jakAl7hMbb
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip