Automatic update from web-platform-testsRevert "Move a test for min-content for a soft-hyphen to wpt"
This reverts commit d37409a17a223249ee661ae504def53bf51b4ce9.
Reason for revert: external/wpt/css/css-sizing/min-content-soft-hyphen-001.html failed on Windows 10
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Win10/36928
Original change's description:
> Move a test for min-content for a soft-hyphen to wpt
>
> This tests when the inline-size is [min-content]:
> * A `­` produces a break opportunity when computing the
> min-content inline size.
> * The hyphen character generated by `­` is included into
> the min-content inline size.
>
> Originally developed in [CL:1111895].
>
> [min-content]: https://www.w3.org/TR/css-sizing-3/#valdef-width-min-content
> [CL:1111895] https://chromium-review.googlesource.com/c/chromium/src/+/1111895
>
> Bug: 636993
> Change-Id: Ib492b2db023a5169247ca00e5b745e42ec33d197
> Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
> Reviewed-on: https://chromium-review.googlesource.com/1113085
> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#570066}
TBR=cbiesinger@chromium.org,kojii@chromium.org
Change-Id: I3fb91c7c2d66e775a12994734a14afc566d05a3e
No-Presubmit: true
No-Tree-Checks: true
No-Try : true
Bug: 636993
Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng
Reviewed-on: https://chromium-review.googlesource.com/1113667
Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570109}
--
wpt-commits: ce2196e7a345f209ce095ec6c7356f3a6cf168d4
wpt-pr: 11660
MozReview-Commit-ID: A5fo6hI5Szs
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
https://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
https://developer.mozilla.org/en/docs/Creating_a_patch
https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on https://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://www.mozilla.org/firefox/channel/desktop/#nightly