Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1111)

Side by Side Diff: LayoutTests/fast/spatial-navigation/snav-css-nav-direction.html

Issue 17450016: Implementation of CSS3 nav-up/down/left/right properties from CSS3 UI. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Rebased once again to master, fixed layout test. Created 6 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 <!DOCTYPE html>
2 <html>
3 <head>
4 <script src="../../resources/js-test.js"></script>
5 <script src="resources/spatial-navigation-utils.js"></script>
6 <script type="application/javascript">
7 jsTestIsAsync = true;
8
9 var resultMap = [
10 ["Right", "e9"],
11 ["Up", "e9"],
12 ["Right", "e5"],
13 ["Up", "e2"],
14 ["Left", "e4"],
15 ["Left", "e6"],
16 ["Down", "e8"],
17 ["Down", "e5"],
18 ["DONE", "DONE"]
19 ];
20
21 if (window.testRunner) {
22 testRunner.overridePreference("WebKitTabToLinksPreferenceKey", 1);
23 window.internals.settings.setSpatialNavigationEnabled(true);
24 }
25
26 function runTest()
27 {
28 // starting the test itself: get to a known place.
29 document.getElementById("e5").focus();
30
31 initTest(resultMap, finishJSTest);
32 }
33 </script>
34 </head>
35 <style>
36 #e2 {
37 nav-left: #e4;
38 }
39 #e4 {
40 nav-left: #e6;
41 }
42 #e5 {
43 nav-right: #e9;
44 nav-up: #e2;
45 }
46 #e6 {
47 nav-down: #e8;
48 }
49 #e8 {
50 nav-down: #e5;
51 }
52 #e9 {
53 nav-up: #e9;
54 nav-right: #e5;
55 }
56 </style>
57 <body id="some-content" onload="runTest();">
58 <p id="description">
fs 2014/04/14 12:32:01 You could use js-test framework's description(...)
Krzysztof Olczyk 2014/04/17 13:48:40 But you still need physical <div>, don't you? I wa
fs 2014/04/17 15:33:48 The framework will create the elements as needed (
59 This test ensures the correctness of Spatial Navigation when CSS3 nav-up/down/le ft/right properties are set.
60 </p>
61 <table style="text-align: left; width: 100%; margin-left: auto; margin-right: au to;" border="1" cellpadding="2" cellspacing="1">
62 <tbody>
63 <tr>
64 <td style="vertical-align: top; text-align: center;"><a id="e1" href="a">1</a></ td>
65 <td style="vertical-align: top; text-align: center;"><a id="e2" href="a">2</a></ td>
66 <td style="vertical-align: top; text-align: center;"><a id="e3" href="a">3</a></ td>
67 </tr>
68 <tr>
69 <td style="vertical-align: top; text-align: center;"><a id="e4" href="a">4</a></ td>
70 <td style="vertical-align: top; text-align: center;"><a id="e5" href="5">5</td>
71 <td style="vertical-align: top; text-align: center;"><a id="e6" href="a">6</a></ td>
72 </tr>
73 <tr>
74 <td style="vertical-align: top; text-align: center;"><a id="e7" href="a">7</a></ td>
75 <td style="vertical-align: top; text-align: center;"><a id="e8" href="a">8</a></ td>
76 <td style="vertical-align: top; text-align: center;"><a id="e9" href="a">9</a></ td>
77 </tr>
78 </tbody>
79 </table>
80 <div id="console"></div>
fs 2014/04/14 12:32:01 The test framework should provide this too.
Krzysztof Olczyk 2014/04/17 13:48:40 But you still need physical <div>, don't you? I wa
81 </body>
82 </html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698