85c1c4e2b17e12286b897a59c9e2f1727b2bac3c: Bug 1508980 - Add more .eslintrc.js files for dom/ and update .eslintignore. r=Gijs
Mark Banner <standard8@mozilla.com> - Wed, 21 Nov 2018 14:27:27 +0000 - rev 506682
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1508980 - Add more .eslintrc.js files for dom/ and update .eslintignore. r=Gijs Differential Revision: https://phabricator.services.mozilla.com/D12529
c9dfaa111bccdd127209ef5d1bf366de314f5e80: Bug 1508288 - nsHostResolver::mOriginSuffix is not used, we should remove it. r=valentin
Dragana Damjanovic <dd.mozilla@gmail.com> - Tue, 20 Nov 2018 21:58:17 +0000 - rev 506681
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1508288 - nsHostResolver::mOriginSuffix is not used, we should remove it. r=valentin Differential Revision: https://phabricator.services.mozilla.com/D12301
395b95afd795a02a49d609cdbb3857274a02276f: Bug 1487964 - Do not report resource-timing subdocument loads triggered by that subdocument r=bzbarsky
Valentin Gosu <valentin.gosu@gmail.com> - Sat, 17 Nov 2018 19:30:36 +0000 - rev 506680
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1487964 - Do not report resource-timing subdocument loads triggered by that subdocument r=bzbarsky Differential Revision: https://phabricator.services.mozilla.com/D9503
e289b39db880c1c8382b68a7a176d1788504ec9a: Bug 1505066 - Update in-content table styles to use Photon colors and introduce striping on Windows r=ntim,dao
matthias <matthias@kammueller.eu> - Tue, 20 Nov 2018 11:15:37 +0000 - rev 506679
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1505066 - Update in-content table styles to use Photon colors and introduce striping on Windows r=ntim,dao Differential Revision: https://phabricator.services.mozilla.com/D11384
95a0973a373520f582880ac258e3d2ee7b1d914d: Bug 1508845 - Make BlastSubtreeToPieces handle Shadow DOM. r=smaug
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 21 Nov 2018 13:02:24 +0000 - rev 506678
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1508845 - Make BlastSubtreeToPieces handle Shadow DOM. r=smaug We can use the unattach shadow stuff because BlastSubtreeToPieces will remove all the slots. Differential Revision: https://phabricator.services.mozilla.com/D12531
a6d6337f6bada016703226a4d127bdef8936aca9: Bug 1508766 - Update webrender to commit 229436b578701fc74a009d6cedc6b2a3ae313f77 (WR PR #3331). r=kats
WR Updater Bot <graphics-team@mozilla.staktrace.com> - Wed, 21 Nov 2018 12:29:04 +0000 - rev 506677
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1508766 - Update webrender to commit 229436b578701fc74a009d6cedc6b2a3ae313f77 (WR PR #3331). r=kats Differential Revision: https://phabricator.services.mozilla.com/D12534
f5db5f1b269099e7900bebb64470aaf0e2213b58: Bug 1500218 - Set 'Move to Start' and 'Move to End' disabled state according to contextTab and contextTab position r=dao,jaws
Michael Kohler <me@michaelkohler.info> - Wed, 21 Nov 2018 11:30:33 +0000 - rev 506676
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1500218 - Set 'Move to Start' and 'Move to End' disabled state according to contextTab and contextTab position r=dao,jaws Differential Revision: https://phabricator.services.mozilla.com/D9598
824bcd08c85e70d98109b04715b26f139e099ce8: Bug 1504911 - part 5: Make HTMLEditor::InsertTableCellsWithTransaction() create AutoPlaceholderBatch and AutoTopLevelEditSubActionNotifier r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 21 Nov 2018 09:30:40 +0000 - rev 506675
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1504911 - part 5: Make HTMLEditor::InsertTableCellsWithTransaction() create AutoPlaceholderBatch and AutoTopLevelEditSubActionNotifier r=m_kato Currently, calling nsITableEditor.insertTableCell() does not cause dispatching "input" event since it does not create AutoPlaceholderBatch. Additionally, different from InsertTableRowsWithTransaction() and InsertTableColumnsWithTransaction(), it does not create AutoTopLevelEditSubActionNotifier. Because of those APIs should work similarly, we should make it creates both auto class instances. Differential Revision: https://phabricator.services.mozilla.com/D12248
09fd7845a50bad9fa7a579a9e7088828d8155a20: Bug 1504911 - part 4: Make all script for web content dispatch "input" event with proper event interface r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 20 Nov 2018 14:35:38 +0000 - rev 506674
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1504911 - part 4: Make all script for web content dispatch "input" event with proper event interface r=smaug Currently, some "input" event dispatchers in our script dispatch "input" event with UIEvent. This is completely wrong. For conforming to HTML spec, Event is proper event. Additionally, for conforming to Input Events, InputEvent is proper event only on <textarea> or <input> element which has a single line editor. For making us to maintain easier, this patch adds new API, "isInputEventTarget" to MozEditableElement which returns true when "input" event dispatcher should use InputEvent for the input element. Finally, this makes some dispatchers use setUserInput() instead of setting value and dispatching event by themselves. This also makes us to maintain them easier. Note that this does not touch "input" event dispatchers which dispatch events only for chrome (such as URL bar, some pages in about: scheme) for making this change safer as far as possible. Differential Revision: https://phabricator.services.mozilla.com/D12247
7f09364736a089ada819bd73b5e7e28a4f048b3b: Bug 1504911 - part 3: Make TextEditRules::WillSetText() not handle anything when EditAction is eReplaceText r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 20 Nov 2018 14:34:32 +0000 - rev 506673
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1504911 - part 3: Make TextEditRules::WillSetText() not handle anything when EditAction is eReplaceText r=m_kato When all editor text is replaced while handling a user operation, editor needs to dispatch "input" event. Therefore, in such case, i.e., EditAction is eReplaceText, TextEditor::SetTextAsSubAction() needs to handle it instead of TextEditRules::WillSetText(). Differential Revision: https://phabricator.services.mozilla.com/D12246
110224ca92565e84894ce093dea626a62f599057: Bug 1504911 - part 2: Make nsTextEditorState::SetValue() dispatch "input" event if it's called for handling part of user input r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 20 Nov 2018 22:06:37 +0000 - rev 506672
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1504911 - part 2: Make nsTextEditorState::SetValue() dispatch "input" event if it's called for handling part of user input r=smaug When editor is modified as part of user action, aFlags of nsTextEditorState::SetValue() includes eSetValue_BySetUserInput. In this case, TextEditor (if there is) or the method itself (if there is no editor yet) should dispatch "input" event by themselves because we will need to initialize InputEvents more since we're going to implement Input Event specs. Note that even with this patch, password field stops dispatching "input" event with call of HTMLInputElement::SetUserInput(). This is caused by a hidden bug of TextEditRules. This will be fixed in a following patch. Differential Revision: https://phabricator.services.mozilla.com/D12245
48440593d675ccfe5a6893118a7e91cc4b823c3f: Bug 1504911 - part 1: Make all "input" event dispatcher in C++ use new utility method r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 21 Nov 2018 03:59:02 +0000 - rev 506671
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1504911 - part 1: Make all "input" event dispatcher in C++ use new utility method r=smaug Currently, a lot of code dispatch "input" event and some of them dispatch "input" event with wrong interface and/or values. Therefore this patch creates nsContentUtils::DispatchInputEvent() to make all of them dispatch correct event. Unfortunately, due to bug 1506439, we cannot set pointer to refcountable classes of MOZ_CAN_RUN_SCRIPT method to nullptr. Therefore, this patch creates temporary RefPtr<TextEditor> a lot even though it makes damage to the performance if it's in a hot path. This patch makes eEditorInput event dispatched with InternalEditorInputEvent when "input" event should be dispatched with dom::InputEvent. However, this patch uses WidgetEvent whose message is eUnidentifiedEvent and setting WidgetEvent::mSpecifiedEventType to nsGkAtoms::oninput when "input" event should be dispatched with dom::Event because we need to keep that eEditorInput and InternalEditorInputEvent are mapped each other. Differential Revision: https://phabricator.services.mozilla.com/D12244
d4a142e1648b3e341fb0f486d7b15a0bad7e0904: Bug 1504911 - part 0: Add "input" event tests into existing tests r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 20 Nov 2018 14:24:06 +0000 - rev 506670
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1504911 - part 0: Add "input" event tests into existing tests r=smaug It's difficult to create new test which checks "input" events caused by all edit operations especially when text is inserted from our UI. Therefore, this adds "input" event type checks into existing tests. Additionally, this adds new test for MozEditableElement.setUserInput() whose behavior needs to be fixed in this bug. Currently, InputEvent interface should be used only on text controls or contenteditable editor when dispatching "input" event. https://w3c.github.io/input-events/#events-inputevents You may feel odd to use different event interface for same "input" events. However, other browsers also use InputEvent interface only in the cases. So, we should follow them for now. Differential Revision: https://phabricator.services.mozilla.com/D12243
fbebc15cd4f40f0978bf22def0fcf355ce69f27b: Bug 1499758 - Fix potential null pointer deref in WebGLContext::GetVRFrame r=jgilbert
Imanol Fernandez <mortimergoro@gmail.com> - Wed, 21 Nov 2018 10:34:52 +0000 - rev 506669
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1499758 - Fix potential null pointer deref in WebGLContext::GetVRFrame r=jgilbert Differential Revision: https://phabricator.services.mozilla.com/D12480
cfde782a9b546f9282469c932011644db7a396a1: Bug 1507109 - Fix popup notification footer button colors. r=ntim
Dão Gottwald <dao@mozilla.com> - Wed, 21 Nov 2018 11:11:22 +0000 - rev 506668
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1507109 - Fix popup notification footer button colors. r=ntim Differential Revision: https://phabricator.services.mozilla.com/D11867
95902e82a59eef77a3f5cde7014419e1f13ed763: Merge mozilla-central to autoland. a=merge CLOSED TREE
Bogdan Tara <btara@mozilla.com> - Wed, 21 Nov 2018 11:48:53 +0200 - rev 506667
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
658cd029a6a1f60ef28a273803439a3f3b1be0b0: Bug 1507476 - Update Changes panel tests to use helpers for rendered declarations. r=pbro
Razvan Caliman <rcaliman@mozilla.com> - Wed, 21 Nov 2018 08:16:06 +0000 - rev 506666
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1507476 - Update Changes panel tests to use helpers for rendered declarations. r=pbro Depends on D12434 Differential Revision: https://phabricator.services.mozilla.com/D12445
67ae9d05389679fed9f5f3b1a681402c719a90f7: Bug 1507476 - Match exact tracked declaration when renaming a property. r=pbro
Razvan Caliman <rcaliman@mozilla.com> - Tue, 20 Nov 2018 16:36:01 +0000 - rev 506665
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1507476 - Match exact tracked declaration when renaming a property. r=pbro Ensure the exact declaration is matched when aggregating changes and attempting to remove declarations which cancel each other out. Without checking both the index and the property name, we used to lose tracked declarations that were renamed. The test checks for the expected rename behaviour and that renaming the declaration to its original clears any tracked changes. Differential Revision: https://phabricator.services.mozilla.com/D12434
ed977fa7caf89d0cff04c3f270124972c433c908: Bug 1498166 - Test storing into multiple stores (and snapshotting main store) r=chutten
Jan-Erik Rediger <jrediger@mozilla.com> - Mon, 19 Nov 2018 13:01:05 +0000 - rev 506664
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1498166 - Test storing into multiple stores (and snapshotting main store) r=chutten For now we test that storing still works and the main store is still accessed for snapshots and clearing. Depends on D11906 Differential Revision: https://phabricator.services.mozilla.com/D11907
544d3ecf27ab29902f07237a3170b1c8217672a7: Bug 1498166 - Add multi-storage to keyed histograms r=chutten
Jan-Erik Rediger <jrediger@mozilla.com> - Wed, 21 Nov 2018 08:34:09 +0000 - rev 506663
Push 1905 by ffxbld-merge at Mon, 21 Jan 2019 12:33:13 +0000
Bug 1498166 - Add multi-storage to keyed histograms r=chutten This extendes the `KeyedHistogram` to keep track of the multiple stores a histogram can be in. Keyed histograms are stored in a hash table, indexed by the name of the store. It has one optimization to support the majority of cases: a single `main` store. For that it stores a direct pointer to a map from keys to the underlying base::Histogram and skips populating the map. This saves an indirection and memory overhead of actually placing it into a second hash table. For now a snapshot only ever returns data from the main store. Clearing a snapshot only clears the main store. Getting the keys of a keyed histogram will only get it from the main store. (This will change in a follow-up) Depends on D11905 Differential Revision: https://phabricator.services.mozilla.com/D11906
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip