Bug 1633228 [wpt PR 23254] - Fix mobile table, a=testonly
authorAnthony Frehner <afrehner.work@gmail.com>
Tue, 28 Apr 2020 11:45:02 +0000
changeset 527284 3d0acbbb6a8b42f39ecf1cdb3d987cfae45f68c3
parent 527283 7033320aabd295c8b35decc25a9a3a036304741e
child 527285 77c6b30ce09a35a6914fefe2acc2c41e4fd10136
push id114648
push userwptsync@mozilla.com
push dateThu, 30 Apr 2020 19:15:02 +0000
treeherderautoland@2545233d9410 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1633228, 23254
milestone77.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1633228 [wpt PR 23254] - Fix mobile table, a=testonly Automatic update from web-platform-tests for larger tables on mobile, you have to wrap in a div and set overflow to auto so that they'll scroll the div instead of the window -- wpt-commits: 5e7cbed423a3040dc8ca50359dd033a46dba5cf4 wpt-pr: 23254
testing/web-platform/tests/docs/assets/custom.css
testing/web-platform/tests/docs/writing-tests/making-a-testing-plan.md
--- a/testing/web-platform/tests/docs/assets/custom.css
+++ b/testing/web-platform/tests/docs/assets/custom.css
@@ -1,7 +1,11 @@
 div.body {
   min-width: auto;
 }
 
 #video-introduction-transcript iframe {
   max-width: 100%;
+}
+
+.table-container {
+  overflow: auto;
 }
\ No newline at end of file
--- a/testing/web-platform/tests/docs/writing-tests/making-a-testing-plan.md
+++ b/testing/web-platform/tests/docs/writing-tests/making-a-testing-plan.md
@@ -477,28 +477,32 @@ complicated criteria may require [regula
 expressions](https://www.regular-expressions.info/). For that, you can
 [download the WPT
 repository](https://web-platform-tests.org/writing-tests/github-intro.html) and
 use [git](https://git-scm.com) to perform more powerful searches.
 
 The following table lists some common search criteria and examples of how they
 can be expressed using regular expressions:
 
+<div class="table-container">
+
 ```eval_rst
 ================================= ================== ==========================
 Criteria                          Example match      Example regular expression
 ================================= ================== ==========================
 JavaScript identifier references  ``obj.foo()``      ``\bfoo\b``
 JavaScript string literals        ``x = "foo";``     ``(["'])foo\1``
 HTML tag names                    ``<foo attr>``     ``<foo(\s|>|$)``
 HTML attributes                   ``<div foo=3>``    ``<[a-zA-Z][^>]*\sfoo(\s|>|=|$)``
 CSS property name                 ``style="foo: 4"`` ``([{;=\"']|\s|^)foo\s+:``
 ================================= ================== ==========================
 ```
 
+</div>
+
 Bear in mind that searches like this are not necessarily exhaustive. Depending
 on the feature, it may be difficult (or even impossible) to write a query that
 correctly identifies all relevant tests. This strategy can give a helpful
 guide, but the results may not be conclusive.
 
 *Example:* Imagine you're interested in testing how the `src` attribute of the
 `iframe` element works with `javascript:` URLs. Judging only from the names of
 directories, you've found a lot of potential locations for such a test. You