Граф коммитов

586334 Коммитов

Автор SHA1 Сообщение Дата
Boris Zbarsky 277b5fdef5 Bug 1433566 part 11. Stop using nsIDOMText in range code. r=mystor
MozReview-Commit-ID: 2EY6w5YlLCH
2018-03-19 15:15:39 -04:00
Boris Zbarsky bd97c33e79 Bug 1433566 part 10. Stop using nsIDOMText in GetWholeText. r=mystor
MozReview-Commit-ID: 4M4q41mEpgb
2018-03-19 15:15:39 -04:00
Boris Zbarsky 2a617cbb78 Bug 1433566 part 9. Move GetWholeText over into Text.cpp. r=mystor
Just code motion, no changes.

MozReview-Commit-ID: 98LkyuU4mya
2018-03-19 15:15:38 -04:00
Boris Zbarsky 3cf3cb7f7f Bug 1433566 part 8. Convert nsGenericDOMDataNode::GetWholeText to webidl-style calling convention. r=mystor
MozReview-Commit-ID: 1ueFgT3ANRS
2018-03-19 15:15:38 -04:00
Boris Zbarsky b5773bb87d Bug 1433566 part 7. Remove nsIDOMText::GetWholeText. r=mystor
MozReview-Commit-ID: I8ZB56a82ze
2018-03-19 15:15:38 -04:00
Boris Zbarsky 4a8ae909c3 Bug 1433566 part 6. Inline SplitData into its one caller. r=mystor
This is mostly a straightforward copy.  The only change is what happens with
the return value of CloneDataNode: it's cast to Text directly, and the
null-check is replaced by an assert.

MozReview-Commit-ID: B5rnhEOneZn
2018-03-19 15:15:38 -04:00
Boris Zbarsky e554cd082b Bug 1433566 part 5. Convert nsGenericDOMDataNode::SplitData to webidl calling conventions. r=mystor
MozReview-Commit-ID: 255TGkYJd4q
2018-03-19 15:15:38 -04:00
Boris Zbarsky 67e4c8f720 Bug 1433566 part 4. Remove unused aCloneAfterOriginal arg of nsGenericDOMDataNode::SplitData. r=mystor
MozReview-Commit-ID: RUJSiOt7Av
2018-03-19 15:15:38 -04:00
Boris Zbarsky d6f4a41e44 Bug 1433566 part 3. Remove nsIDOMText::SplitText. r=mystor
MozReview-Commit-ID: 1jghu75LKDw
2018-03-19 15:15:38 -04:00
Boris Zbarsky ba095e218b Bug 1433566 part 2. Remove use of nsIDOMText from JS. r=mystor
MozReview-Commit-ID: LtAhn223y0s
2018-03-19 15:15:37 -04:00
Boris Zbarsky 294c770343 Bug 1433566 part 1. Add a non-virtual nsINode::IsText(). r=mystor
MozReview-Commit-ID: Ik5hGubUDqX
2018-03-19 15:15:37 -04:00
Luke Wagner 028218ea86 Bug 1445966 - Baldr: move wasm trap state from JSRuntime to JitActivation (r=bbouvier)
--HG--
extra : rebase_source : 3ce4922fa886a6dfb0d6fbcfab9e94e347d763f6
2018-03-19 12:42:05 -05:00
David Keeler aa1464d4a7 bug 1444265 - break a potential cycle in BackgroundFileSaver to prevent leaks r=jduell
BackgroundFileSaver holds a reference to its nsIBackgroundFileSaverObserver
(observer). If such an observer has an enclosure that captures the
BackgroundFileSaver itself (as in test_backgroundfilesaver.js), this causes a
cycle that won't be caught by the cycle collector. Thus, we have to manually
break the cycle when we're done with the observer (in
BackgroundFileSaver::NotifySaveComplete). Note that this currently relies on the
fact that this implementation requires that Finish always be called (see remarks
in nsIBackgroundFileSaver.idl).

MozReview-Commit-ID: GOO9q2vFRso

--HG--
extra : rebase_source : f62b0ec513e0b681da3e76c0af31077d2fa03fea
extra : amend_source : 2b3a11d4b17df10705bad38e02b6ce130b456448
2018-03-14 15:02:49 -07:00
Stephen A Pohl 60df3274c7 Bug 1423261: Add crash message annotations to our crash reports to help investigate shutdown crashes due to open message channels when they are expected to be closed. Nightly only. r=jimm 2018-03-19 13:19:15 -04:00
Ryan VanderMeulen 38359cd40f Bug 1445105 - Remove various MSVC de-optimizations used to work around compiler bugs which are no longer needed. r=dmajor
This reverts the following bugs: 703135, 977538, 1274450, 1403220

--HG--
extra : rebase_source : c63585a915c5b9ea987fd035dbb5ecb21cb6246e
2018-03-19 12:42:01 -04:00
Sebastian Hengst fac6016d5c Backed out changeset ec272d453729 (bug 1356558) for failing new crashtest. CLOSED TREE 2018-03-19 18:52:01 +02:00
Lee Salzman f0cb87c218 Bug 1438917 - limit allocations in SkTDynamicHash. r=jrmuizel
MozReview-Commit-ID: 1d3Tngi6Uek
2018-03-19 11:56:14 -04:00
Honza Bambas 0998499d37 Bug 1444975 - Switch to HTTP throttling v2 algorithm. r=valentin
--HG--
extra : amend_source : fcda726deb971ab73cd5df288af104064243351c
2018-03-12 11:23:00 -04:00
layely 17a5e3cfc6 Bug 1445732 - Avoid invoking mute and unmute methods for lazy-browsers to prevent premature insertion. r=jaws
--HG--
extra : rebase_source : f8e5e4283d2625ec140fe08092e3fccd64c8368a
2018-03-18 03:23:07 +00:00
Emilio Cobos Álvarez 4211f7ecdb Bug 1356558: Crashtest. r=me
MozReview-Commit-ID: oHokeAhYiY
2018-03-19 16:33:07 +01:00
Honza Bambas e5943f18e9 Bug 1445796 - Add logging of a calling JS script to more http channel methods. r=valentin 2018-03-16 09:28:00 -04:00
André Bargull c22fbf595e Bug 1446061 - Follow-up changes from unused parameter removal review. r=tcampbell 2018-03-15 12:23:33 -07:00
Richard Pospesel 2ba1e92974 Bug 1441327 - Allow for seccomp filtering of socket(AF_INET/AF_INET_6) calls on Linux when using UNIX Domain Sockets for SOCKS Proxy. r=bagder
The initialization path for the SOCKS proxy in firefox involves creating
a generic AF_INET socket, and then replacing it if the actual
configuration requires something else (either AF_INET6 or AF_LOCAL).
With syscall filtering configured to return an error in the event of
AF_INET or AF_INET6 socket creation, this initialization path fails.  We
would like this capability so that we can prevent firefox from making
network requests outside of the Tor proxy.

This patch adds a check in the initial socket creation path to see if
the SOCKS proxy host begins with file:// with the assumption that such
URIs point to a UNIX Domain Socket (on Linux+macOS only).  In that case,
we create an AF_LOCAL socket rather than the requested type.  A similar
check for Windows already exists to determine if the proxy is actually a
named pipe.

In the subsequent replacing step no work occurs as the passed in socket
matches the type we need, so no changes need to be made there.

NOTE: With this change there is still a one-time request for an AF_INET6
socket that occurs.  This code path exists to determine whether the
system supports IPv6; if socket(AF_INET6...) fails then it is assumed
that the system does not.  However, this check only affects code that is
unreachable when using AF_LOCAL sockets so it seems safe leave as it is.
However, this does mean that firefox will still be incompatible with
seccomp policies which kill the calling thread in the event of a
socket(AF_INET6,...) call.
2018-03-07 12:58:00 -05:00
Honza Bambas f5cc301b66 Bug 1446117 - Make sure we also mark timeout epoch on a network socket when we are polling it for read/write, fix regression from bug 1444160. r=valentin 2018-03-19 07:48:00 -04:00
Jan-Erik Rediger 9dbde32f95 Bug 1443599 - Stop reporting legacy Telemetry component `childPayloads`. r=chutten
--HG--
extra : histedit_source : 3bd881b0763817905c8544af50ef23ae3d83e1e2
2018-03-19 11:33:25 +01:00
Honza Bambas c940bbdf06 Bug 1430659 - Network requests in "blocked" state for long time (1+ minute) when ipv6 hosts are no longer available. r=valentin 2018-03-16 09:06:00 -04:00
Samuel Thibault 39ed413777 Bug 1346535 - atk: Introduce U+FEFF characters to match AT-SPI offsets with DOM offsets. r=surkov, r=dbaron 2018-03-16 15:57:00 -04:00
Jan de Mooij 22ab8f3704 Bug 1446766 part 3 - Remove unused setReturnDoubleRegs methods. r=nbp 2018-03-19 14:31:53 +01:00
Jan de Mooij 31dc39303a Bug 1446766 part 2 - Move some wasm code from CodeGenerator-shared.cpp to CodeGenerator.cpp. r=bbouvier 2018-03-19 14:31:25 +01:00
Jan de Mooij 989e24aa7d Bug 1446766 part 1 - Use a macro to declare CodeGenerator visit methods. r=nbp 2018-03-19 14:30:50 +01:00
Emilio Cobos Álvarez a93be87a5c Bug 1446507: Don't unnecessarily notify the document for shadow style changes if it's not in the document. r=xidorn
Summary:
When the host is bound to the document, it'll also re-BindToTree the shadow
tree, which will update the stylesheets and all that.

Reviewers: xidorn

Bug #: 1446507

Differential Revision: https://phabricator.services.mozilla.com/D742

MozReview-Commit-ID: fBLq5owB7U
2018-03-19 13:56:53 +01:00
arthur.iakab 4dec00af02 Merge mozilla-central to mozilla-inbound 2018-03-19 12:51:12 +02:00
arthur.iakab 877c99c523 Merging mozilla-inbound to mozilla central a=merge 2018-03-19 12:43:31 +02:00
Emilio Cobos Álvarez e1643f5ac2 Bug 1446666: Assert that there are no frames for content outside of the flat tree. r=smaug
Summary: This would've caught stuff like bug 1438210 earlier.

Reviewers: smaug

Bug #: 1446666

Differential Revision: https://phabricator.services.mozilla.com/D756

MozReview-Commit-ID: 1cptyygiQRj
2018-03-19 11:11:48 +01:00
Emilio Cobos Álvarez 6c449a5e5c Bug 1446597: Remove unused Node.getMutationObservers. r=smaug
Summary:
I'm happy to keep it around if you think having the test_mutationobservers check
is useful.

MozReview-Commit-ID: LbWvJiO9LRZ

Reviewers: smaug

Bug #: 1446597

Differential Revision: https://phabricator.services.mozilla.com/D750
2018-03-19 11:11:48 +01:00
vinoth 28c7245f64 Bug 1391823 - Don't run |finish() called multiple times| for dom/security/test/mixedcontentblocker/test_frameNavigation.html. r=ckerschb
Reviewers: ckerschb

Reviewed By: ckerschb

Subscribers: ckerschb

Bug #: 1391823

Differential Revision: https://phabricator.services.mozilla.com/D562

--HG--
extra : rebase_source : 0ff9fc78d2ca00c2c347f14167de34e31ded1967
extra : amend_source : f2a350607bb0645e3140b51cc57353a50f7c2261
2018-03-19 12:00:55 +02:00
sotaro 04da311500 Bug 1443671 - Add crashtest r=nical 2018-03-19 18:54:05 +09:00
Zhang Junzhi 6f951120b1 Bug 1446724 - Lets plugins still receive original delta values instead of horizontalized values if the default action for wheel scrolling is horizontalizing vertical wheel scrolling. r=masayuki
Unlike a DOM wheel event listeners which receive original delta values, plugins
receive horizontalized ones. It's not reasonable to not send original values to
plugins.

Plugin developers can do any delta adjustment, and they are also capable of
DIRECTLY getting what inputs the user is manipulating, that is to say,
developers can horizontalize scrolling for [Shift+Vertical Wheel] or other other
inputs if they want, it's just their matter; conversely, they aren't capable of
getting what delta adjustment their upstream has already encapsulated for them.
So it's not reasonable to send adjusted delta values to plugins.

This patch restores horizontalized delta values to the original for plugins.

MozReview-Commit-ID: IX8XJn0lbKq

--HG--
extra : rebase_source : ea9abef4706701e2c43ee06563bd10bc0a863614
2018-03-19 13:50:49 +08:00
Felipe Gomes 1fb3ac97b7 Bug 1429177 - Policy: Set network proxy settings. r=mixedpuppy 2018-03-19 02:15:50 -03:00
Hiroyuki Ikezoe df1a0e7203 Bug 1444177 - Tweak expected restyle count for the test case where finite animation is unthrottled in out-of-view element. r=birtles
It might be possible that the animation does not start being restyled in the
initial frame.  Eventually we should drop tweakExpectedRestyleCount in bug
1425778 and replace it with a function that waits for animation.ready and waits
to start being restyled something like this;

  async function waitForAnimationReadyToBeRestyled(aAnimation) {
    await aAnimation.ready;

    if (animationStartsRightNow(aAnimation)) {
      await waitForFrame();
    }
  }

MozReview-Commit-ID: ByN25hMAK76

--HG--
extra : rebase_source : 6dd3a44661905ffff7bce748540572df2d40425b
2018-03-19 12:46:23 +09:00
Tooru Fujisawa 98bed8bd01 Bug 1442465 - followup: Wait for session store update in browser/components/migration/tests/browser/browser_undo_notification.js. r=me 2018-03-19 12:40:46 +09:00
Masayuki Nakano 1c1a60c08d Bug 1446253 - Make EventUtils.synthesizeComposition() dispatch keydown and keyup event in default r=smaug
We'll start to dispatch keydown event and keyup event even during composition.
So, for testing those events won't break our UI, we should make
EventUtils.synhtesizeComposition() and EventUtils.synthesizeCompositionChange()
dispatch keydown event and keyup event even if callers don't specify keyboard
event explicitly.

Typically, "keydown" event is marked as "processed by IME", i.e., keyCode
value is set to DOM_VK_PROCESSKEY and key is set to "Process", with our
widget which handles native IME and key input.  On the other hand, "keyup"
is NOT marked as so.

Therefore, this patch makes TextInputProcessor emulates this behavior without
any new special flags.  And for making possible to emulate special cases,
this patch adds two flags to nsITextInputProcessor.  One is
KEY_DONT_MARK_KEYDOWN_AS_PROCESSED.  The other is KEY_MARK_KEYUP_AS_PROCESSED.
Unfortunately, those flags have opposite meaning but this must be better than
making necessary to one flag for emulating usual keydown/keyup events.

Finally, this makes some tests specify better keyboard information to
synthesizeComposition() and synthesizeCompositionChange() to emulate
actual keyboard events during composition.

MozReview-Commit-ID: ItYaXILkNQE

--HG--
extra : rebase_source : e50cc77c1efbc12686d7ea334d41926c7392b30d
2018-03-16 22:35:07 +09:00
Glenn Watson 720853bca4 servo: Merge #20334 - Update WR (radial gradient optimizations) (from glennw:update-wr-rad); r=jdm
Source-Repo: https://github.com/servo/servo
Source-Revision: 52205e8483da470bcf1960bf6adb1f98c7fc452d

--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : efe0648a4d48feb14c8249888788d9b8a0857f43
2018-03-18 17:44:42 -04:00
Makoto Kato ef2b99f490 Bug 1446270 - Android/arm target should turn on crash reporter as default. r=froydnj
target value of Anndroid/arm is arm-unknown-linux-androideabi, so arm-*-linux*
matches on android/arm and MOZ_CRASHREPORTER is unset as default option.

Since taskcluster's build adds --enable-crashrepoter as default, we should set
it as developer's default too.

MozReview-Commit-ID: 8V6sWAN07F9

--HG--
extra : rebase_source : b4a26eea2d53eb8b53cc49e972d9d41b32d4ec97
2018-03-16 16:38:14 +09:00
Tooru Fujisawa a6e9caf67e Bug 1442465 - Part 6: Stop returning a Promise from BrowserTestUtils.removeTab. r=dao 2018-03-19 11:16:49 +09:00
Tooru Fujisawa f25e652e9b Bug 1442465 - Part 5: Workaround for some BrowserTestUtils.removeTab cases. r=dao 2018-03-19 11:16:49 +09:00
Tooru Fujisawa 1adba8c1fc Bug 1442465 - Part 4.2: Stop unnecessarily awaiting on BrowserTestUtils.removeTab (simple part). r=dao 2018-03-19 11:16:45 +09:00
Tooru Fujisawa d6dc027000 Bug 1442465 - Part 4.1: Stop unnecessarily awaiting on BrowserTestUtils.removeTab (non-simple part). r=dao 2018-03-19 11:12:14 +09:00
Tooru Fujisawa 0047ec3b43 Bug 1442465 - Part 3: Use BrowserTestUtils.{waitForTabClosing,waitForSessionStoreUpdate} instead of BrowserTestUtils.removeTab. r=dao 2018-03-19 11:12:13 +09:00
Tooru Fujisawa 3038c58523 Bug 1442465 - Part 2: Use BrowserTestUtils.{waitForTabClosing,waitForSessionStoreUpdate} instead of BrowserTestUtils.tabRemoved. r=dao 2018-03-19 11:12:13 +09:00