qutebrowser/tests/end2end/data/hints/html/simple.html

<!DOCTYPE html>

<!-- target: hello.txt -->

<html>
    <head>
        <meta charset="utf-8">
        <title>Simple link</title>
    </head>
    <body>
        <a href="/data/hello.txt" id="link">Follow me!</a>
    </body>
</html>
tests: Add first end-to-end test for hints. This is based on HTML files with a global YAML comment, currently with "target" as the only allowed key. The tests then do this: - Open a HTML file in data/hints/html - Start hinting - Make sure only one hint is visible - Follow it, and make sure the page mentioned in "target:" is reached Some ideas for the future: - A "scroll" key, to scroll before hinting - A "zoom" key, to zoom - Multiple hints via a list - Checking position of hints? - A mode to manually check the pages (to check hint positions) 2016-02-18 07:35:14 +01:00			`<!DOCTYPE html>`

			`<!-- target: hello.txt -->`

			`<html>`
			`<head>`
			`<meta charset="utf-8">`
			`<title>Simple link</title>`
			`</head>`
			`<body>`
BDD: Use :click-element instead of hints 2016-08-18 16:13:38 +02:00			`<a href="/data/hello.txt" id="link">Follow me!</a>`
tests: Add first end-to-end test for hints. This is based on HTML files with a global YAML comment, currently with "target" as the only allowed key. The tests then do this: - Open a HTML file in data/hints/html - Start hinting - Make sure only one hint is visible - Follow it, and make sure the page mentioned in "target:" is reached Some ideas for the future: - A "scroll" key, to scroll before hinting - A "zoom" key, to zoom - Multiple hints via a list - Checking position of hints? - A mode to manually check the pages (to check hint positions) 2016-02-18 07:35:14 +01:00			`</body>`
			`</html>`