42df425823e9debac0c292d1c2f357d599abab5d: Bug 1332234 - P1. Add support for AMD's VP9 hardware decoder. r=cpearce draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 04 Aug 2017 18:33:20 +0200 - rev 648178
Push 74655 by bmo:jyavenard@mozilla.com at Thu, 17 Aug 2017 10:13:04 +0000
Bug 1332234 - P1. Add support for AMD's VP9 hardware decoder. r=cpearce This enables VP9 decoding on Windows with AMD graphic adapters supporting it. The AMD VP9 MFT only works 720 and more pixels high. The system will attempt the following decoding configuration: 1- AMD VP9 MFT 2- Microsoft VP9 MFT (only if DXVA is enabled) 3- FFmpeg ffvp9 software decoder MozReview-Commit-ID: IP2eHZEQ7Tj
8d9235d2d709ea48b90682fc64149596fc3a04c3: Bug 863246 - Add test cases draft
Chung-Sheng Fu <cfu@mozilla.com> - Thu, 08 Jun 2017 17:54:41 +0800 - rev 648177
Push 74654 by bmo:cfu@mozilla.com at Thu, 17 Aug 2017 10:10:48 +0000
Bug 863246 - Add test cases MozReview-Commit-ID: 9oXWNOREemX
9ba76704479d3aa826f4b400dcb830bfbe422a52: Bug 863246 - Fix test failures draft
Chung-Sheng Fu <cfu@mozilla.com> - Wed, 19 Jul 2017 17:30:01 +0800 - rev 648176
Push 74654 by bmo:cfu@mozilla.com at Thu, 17 Aug 2017 10:10:48 +0000
Bug 863246 - Fix test failures MozReview-Commit-ID: 8tUr27zvs8z
17e8d2243917705203878d81af27468d8d3ca2d4: Bug 863246 - Use system principal to load debugger scripts draft
Chung-Sheng Fu <cfu@mozilla.com> - Mon, 07 Aug 2017 15:55:39 +0800 - rev 648175
Push 74654 by bmo:cfu@mozilla.com at Thu, 17 Aug 2017 10:10:48 +0000
Bug 863246 - Use system principal to load debugger scripts MozReview-Commit-ID: DPvbR1As2UV
b2b82c2dab3267d2f949101608084dc85dd2d887: Bug 863246 - Move resources that need to be exposed to web content to locations that are marked as contentaccessible draft
Chung-Sheng Fu <cfu@mozilla.com> - Thu, 08 Jun 2017 17:52:46 +0800 - rev 648174
Push 74654 by bmo:cfu@mozilla.com at Thu, 17 Aug 2017 10:10:48 +0000
Bug 863246 - Move resources that need to be exposed to web content to locations that are marked as contentaccessible MozReview-Commit-ID: ArhSHKPYOr8
1d9c236b48191cce07d6b018a43951c6ffb0edd6: Bug 863246 - Content can only load resource:// URIs declared content-accessible in manifests draft
Chung-Sheng Fu <cfu@mozilla.com> - Thu, 08 Jun 2017 17:44:09 +0800 - rev 648173
Push 74654 by bmo:cfu@mozilla.com at Thu, 17 Aug 2017 10:10:48 +0000
Bug 863246 - Content can only load resource:// URIs declared content-accessible in manifests bz: caps/nsScriptSecurityManager.cpp billm: browser/extensions/activity-stream/jar.mn browser/extensions/onboarding/jar.mn chrome/RegistryMessageUtils.h chrome/nsChromeRegistry.h chrome/nsChromeRegistryChrome.cpp chrome/nsChromeRegistryContent.cpp netwerk/protocol/res/SubstitutingProtocolHandler.cpp netwerk/protocol/res/SubstitutingProtocolHandler.h netwerk/protocol/res/nsIResProtocolHandler.idl netwerk/protocol/res/nsISubstitutingProtocolHandler.idl netwerk/protocol/res/nsResProtocolHandler.cpp netwerk/protocol/res/nsResProtocolHandler.h xpcom/components/ManifestParser.cpp MozReview-Commit-ID: 1RXeNn7jdBf
838dae06bd880a5506722f63b2ad520e64e647a7: Bug 1391165 - part4: nsIEditor::EndOfDocument() should be implemented with an internal method which takes pointer to Selection r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 17 Aug 2017 17:08:22 +0900 - rev 648172
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1391165 - part4: nsIEditor::EndOfDocument() should be implemented with an internal method which takes pointer to Selection r?smaug EditorBase::GetSelection() sometimes appears in profile. So, it shouldn't be called in nsIEditor::EndOfDocument() if the callers of nsIEditor::EndOfDocument() has a pointer to Selection. This patch adds EditorBase::CollapseSelectionToEnd() for the internal method and make all callers of nsIEditor::EndOfDocument() use it. MozReview-Commit-ID: 8H4ThxzdKDf
2198db8eb9433d4de96357ebc55f20c2e870cadf: Bug 1391165 - part3: TextEditRules::CollapseSelectionToTrailingBRIfNeeded() should use EditorBase::GetChildOffset() only when it's necessary r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 17 Aug 2017 16:48:49 +0900 - rev 648171
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1391165 - part3: TextEditRules::CollapseSelectionToTrailingBRIfNeeded() should use EditorBase::GetChildOffset() only when it's necessary r?smaug In most cases, TextEditRules::CollapseSelectionToTrailingBRIfNeeded() doesn't use the index anymore. Therefore, it should stop using EditorBase::GetNodeLocation() and use EditorBase::GetChildOffset() only when the offset is necessary. MozReview-Commit-ID: 9vGcLnTUnsu
3df9968891bdf338a4774f15d1a298f24018ebf7: Bug 1391165 - part2: TextEditRules::CollapseSelectionToTrailingBRIfNeeded() should use nsINode::GetNextSibling() for retrieving next child of a node r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 17 Aug 2017 16:35:30 +0900 - rev 648170
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1391165 - part2: TextEditRules::CollapseSelectionToTrailingBRIfNeeded() should use nsINode::GetNextSibling() for retrieving next child of a node r?smaug nsINode::GetChildAt() is too expensive if it's used for next sibling of a node. This patch makes it use nsINode::GetNextSibling() instead. MozReview-Commit-ID: CAC7gFNo77w
3d126e6b5fb7dd2e88be9677d831e96b2a35c2da: Bug 1391165 - part1: EditorBase::GetChildOffset() and EditorBase::GetNodeLocation() shouldn't use nsINode::IndexOf() as far as possible r?smaug draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 17 Aug 2017 16:24:16 +0900 - rev 648169
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1391165 - part1: EditorBase::GetChildOffset() and EditorBase::GetNodeLocation() shouldn't use nsINode::IndexOf() as far as possible r?smaug nsINode::IndexOf() is expensive especially when it's in a hot path, it's too expensive. So, EditorBase::GetChildOffset() and EditorBase::GetNodeLocation() should check child's siblings first. If some of them are nullptr, it means that it's first child or last child of the parent. Note that EditorBase::GetChildOffset() may return wrong index if it's called while aChild is being removed from aParent or aParent isn't actual parent of aChild. However, they are check if result is -1 with MOZ_ASSERT(). Therefore, it's safe to assume that aParent is always the parent of aChild and it won't be called from ContentRemoved() of mutation observers. MozReview-Commit-ID: 8JdYWuZbHe5
156338443161f18d12ae45afa3b81c0cb53b4144: Bug 1390831 - Make test_bug635636.html e10s-aware r?ehsan draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 16 Aug 2017 21:03:18 +0900 - rev 648168
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1390831 - Make test_bug635636.html e10s-aware r?ehsan test_bug655636.html refers gBrowser, however, it's available only in chrome process and it's referred only for listening to "pageshow" event instead of "load" event of the data URI. So, we must be able to use "unload" event of the previous URL instead. Although, this testcase (even without this change) won't cause crash even if backing out the patch for bug 635636 anymore. MozReview-Commit-ID: B8qOwVZqZQm
267df6704f7b06636ce748cd2499cc7b3199317a: Bug 1375502 - part6: Rename endIndx of nsContentIterator::InitInternal() to aEndOffset r?mats draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 16 Aug 2017 22:14:40 +0900 - rev 648167
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1375502 - part6: Rename endIndx of nsContentIterator::InitInternal() to aEndOffset r?mats MozReview-Commit-ID: 2Z817Xyx1JN
b4be874c42f8fb5f4329813c870c92fe6a0cef0e: Bug 1375502 - part5: Rename startIndx of nsContentIterator::InitInternal() to aStartOffset r?mats draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 16 Aug 2017 22:13:47 +0900 - rev 648166
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1375502 - part5: Rename startIndx of nsContentIterator::InitInternal() to aStartOffset r?mats MozReview-Commit-ID: 9NGxFjM5Mox
dfccd1c610f8be18e1759f7197dd34aff323942a: Bug 1375502 - part4: Rename endNode of nsContentIterator::InitInternal() to aEndContainer r?mats draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 16 Aug 2017 22:12:28 +0900 - rev 648165
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1375502 - part4: Rename endNode of nsContentIterator::InitInternal() to aEndContainer r?mats MozReview-Commit-ID: 3Dq8Ptpy6pN
7cf8ef15209e8345d37f5eb6ec15e5e57a55d196: Bug 1375502 - part3: Rename startNode of nsContentIterator::InitInternal() to aStartContainer r?mats draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 16 Aug 2017 22:11:11 +0900 - rev 648164
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1375502 - part3: Rename startNode of nsContentIterator::InitInternal() to aStartContainer r?mats MozReview-Commit-ID: 9fXIKhB03Mx
4d2154739d0f8a8a2d5c06854f4b3f5a6d874271: Bug 1375502 - part2: Add nsIContentIterator::Init(nsINode*, uint32_t, nsINode*, uint32_t) r?mats draft
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 26 Jun 2017 17:26:27 +0900 - rev 648163
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1375502 - part2: Add nsIContentIterator::Init(nsINode*, uint32_t, nsINode*, uint32_t) r?mats nsIContentIterator::Init() takes nsRange but it's too expensive for some users. So, there should be another Init() which can be specified a range in DOM tree with 2 pairs of nsINode* and uint32_t. MozReview-Commit-ID: 6JXic0KOM2d
74d617cac5d6ae34c6624827cf01af4702c5998e: Bug 1375502 - part1: ContentEventHandler shouldn't use nsRange for temporary use r?mats draft
Masayuki Nakano <masayuki@d-toybox.com> - Fri, 23 Jun 2017 13:21:47 +0900 - rev 648162
Push 74653 by masayuki@d-toybox.com at Thu, 17 Aug 2017 10:09:29 +0000
Bug 1375502 - part1: ContentEventHandler shouldn't use nsRange for temporary use r?mats Allocating and initializing nsRange is too expensive especially for temporary use. However, ContentEventHandler uses nsRange only for representing two DOM points. So, it should use simpler helper class, RawRange, for reducing some unnecessary runtime cost. Note that this still uses nsRange for initializing nsIContentIterator. This will be fixed by the following patch. MozReview-Commit-ID: 5TUy6yJf7HA
e02be2778c9383a97c9ab5f626a34dbbb36c75ae: Bug 1389640 - Restore focus states for url bar in light/dark themes. r=dao draft
Dale Harvey <dale@arandomurl.com> - Thu, 17 Aug 2017 11:04:58 +0100 - rev 648161
Push 74652 by bmo:dharvey@mozilla.com at Thu, 17 Aug 2017 10:05:57 +0000
Bug 1389640 - Restore focus states for url bar in light/dark themes. r=dao MozReview-Commit-ID: K3Jy8CXOkDS
39d42c06e5ae1816f9daa0ea426ce52d469be1da: Bug 1390550 - Update to latest libhyphen code from upstream. r=ryanvm
Jonathan Kew <jkew@mozilla.com> - Thu, 17 Aug 2017 09:58:29 +0100 - rev 648160
Push 74652 by bmo:dharvey@mozilla.com at Thu, 17 Aug 2017 10:05:57 +0000
Bug 1390550 - Update to latest libhyphen code from upstream. r=ryanvm
6b2167c58ec0a29cb1c79a7c4da632f011e543cb: Bug 1390437 - Add NotifyInvalidation after EndTransaction for layers-free mode. r=kats draft
Ethan Lin <ethlin@mozilla.com> - Tue, 15 Aug 2017 16:54:12 +0800 - rev 648159
Push 74651 by bmo:ethlin@mozilla.com at Thu, 17 Aug 2017 09:55:02 +0000
Bug 1390437 - Add NotifyInvalidation after EndTransaction for layers-free mode. r=kats For layers-free mode, we still need to call NotifyInvalidation to trigger FireDOMPaintEvent. It should be fine to pass an empty rect since we always take full snapshot for WR. MozReview-Commit-ID: EzzQi2C5aRQ
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip