2022-09-19 05:32:30 -05:00
|
|
|
// This test checks the position of the `i` for the notable traits.
|
2024-04-05 14:38:55 -05:00
|
|
|
include: "utils.goml"
|
2023-04-11 12:11:34 -05:00
|
|
|
go-to: "file://" + |DOC_PATH| + "/test_docs/struct.NotableStructWithLongName.html"
|
2022-09-19 05:32:30 -05:00
|
|
|
show-text: true
|
2024-04-20 07:53:14 -05:00
|
|
|
|
|
|
|
define-function: (
|
|
|
|
"check-notable-tooltip-position",
|
|
|
|
[x, i_x],
|
|
|
|
block {
|
|
|
|
// Checking they have the same y position.
|
|
|
|
compare-elements-position: (
|
2024-07-06 19:12:53 -05:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//a[normalize-space()='NotableStructWithLongName']",
|
2024-04-20 07:53:14 -05:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
["y"],
|
|
|
|
)
|
|
|
|
// Checking they don't have the same x position.
|
|
|
|
compare-elements-position-false: (
|
2024-07-06 19:12:53 -05:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//a[normalize-space()='NotableStructWithLongName']",
|
2024-04-20 07:53:14 -05:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
["x"],
|
|
|
|
)
|
|
|
|
// The `i` should be *after* the type.
|
|
|
|
assert-position: (
|
2024-07-06 19:12:53 -05:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//a[normalize-space()='NotableStructWithLongName']",
|
2024-04-20 07:53:14 -05:00
|
|
|
{"x": |x|},
|
|
|
|
)
|
|
|
|
assert-position: (
|
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
{"x": |i_x|},
|
|
|
|
)
|
|
|
|
},
|
2022-10-26 16:42:53 -05:00
|
|
|
)
|
2024-04-20 07:53:14 -05:00
|
|
|
|
|
|
|
define-function: (
|
|
|
|
"check-notable-tooltip-position-complete",
|
|
|
|
[x, i_x, popover_x],
|
|
|
|
block {
|
|
|
|
call-function: ("check-notable-tooltip-position", {"x": |x|, "i_x": |i_x|})
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
|
|
|
compare-elements-position-near: (
|
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
"//*[@class='tooltip popover']",
|
|
|
|
{"y": 30}
|
|
|
|
)
|
|
|
|
compare-elements-position-false: (
|
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
"//*[@class='tooltip popover']",
|
|
|
|
["x"]
|
|
|
|
)
|
|
|
|
assert-position: (
|
|
|
|
"//*[@class='tooltip popover']",
|
|
|
|
{"x": |popover_x|}
|
|
|
|
)
|
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
move-cursor-to: "//h1"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
},
|
2022-10-26 16:42:53 -05:00
|
|
|
)
|
2024-04-20 07:53:14 -05:00
|
|
|
|
|
|
|
// We start with a wide screen.
|
|
|
|
set-window-size: (1100, 600)
|
|
|
|
call-function: ("check-notable-tooltip-position-complete", {
|
|
|
|
"x": 677,
|
|
|
|
"i_x": 955,
|
|
|
|
"popover_x": 463,
|
|
|
|
})
|
2022-09-19 05:32:30 -05:00
|
|
|
|
|
|
|
// Now only the `i` should be on the next line.
|
2023-04-11 12:11:34 -05:00
|
|
|
set-window-size: (1055, 600)
|
2022-09-19 05:32:30 -05:00
|
|
|
compare-elements-position-false: (
|
2024-07-06 19:12:53 -05:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//a[normalize-space()='NotableStructWithLongName']",
|
2023-01-26 14:32:33 -06:00
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
2024-04-01 14:11:22 -05:00
|
|
|
["y", "x"],
|
2022-09-19 05:32:30 -05:00
|
|
|
)
|
|
|
|
|
|
|
|
// Now both the `i` and the struct name should be on the next line.
|
2023-04-11 12:11:34 -05:00
|
|
|
set-window-size: (980, 600)
|
2024-04-20 07:53:14 -05:00
|
|
|
call-function: ("check-notable-tooltip-position", {
|
|
|
|
"x": 245,
|
|
|
|
"i_x": 523,
|
|
|
|
})
|
2022-09-19 05:32:30 -05:00
|
|
|
|
|
|
|
// Checking on mobile now.
|
2023-04-11 12:11:34 -05:00
|
|
|
set-window-size: (650, 600)
|
2024-10-09 14:23:20 -05:00
|
|
|
wait-for-size: ("body", {"width": 650})
|
2024-04-20 07:53:14 -05:00
|
|
|
call-function: ("check-notable-tooltip-position-complete", {
|
2024-10-08 13:53:11 -05:00
|
|
|
"x": 25,
|
|
|
|
"i_x": 303,
|
2024-04-20 07:53:14 -05:00
|
|
|
"popover_x": 0,
|
|
|
|
})
|
2022-09-19 05:32:30 -05:00
|
|
|
|
2022-11-07 22:18:01 -06:00
|
|
|
// Now check the colors.
|
|
|
|
define-function: (
|
|
|
|
"check-colors",
|
2024-04-01 14:11:22 -05:00
|
|
|
[theme, header_color, content_color, type_color, trait_color, link_color],
|
2023-01-06 08:18:51 -06:00
|
|
|
block {
|
2023-04-11 12:11:34 -05:00
|
|
|
go-to: "file://" + |DOC_PATH| + "/test_docs/struct.NotableStructWithLongName.html"
|
2022-11-07 22:18:01 -06:00
|
|
|
// This is needed to ensure that the text color is computed.
|
2023-01-06 08:18:51 -06:00
|
|
|
show-text: true
|
2022-11-07 22:18:01 -06:00
|
|
|
|
2024-04-05 14:38:55 -05:00
|
|
|
call-function: ("switch-theme", {"theme": |theme|})
|
2022-11-07 22:18:01 -06:00
|
|
|
|
2023-05-23 19:19:35 -05:00
|
|
|
assert-css: (
|
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
{"color": |content_color|},
|
|
|
|
ALL,
|
|
|
|
)
|
|
|
|
|
2023-01-26 14:32:33 -06:00
|
|
|
move-cursor-to: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
rustdoc: add interaction delays for tooltip popovers
Designing a good hover microinteraction is a matter of guessing
user intent from what are, literally, vague gestures. In this case,
guessing if hovering in our out of the tooltip base is intentional
or not.
To figure this out, a few different techniques are used:
* When the mouse pointer enters a tooltip anchor point, its hitbox
is grown on the bottom, where the popover is/will appear. This was
already there before this commit: search "hover tunnel" in
rustdoc.css for the implementation.
* This commit adds a delay when the mouse pointer enters the base
anchor, in case the mouse pointer was just passing through and the
user didn't want to open it.
* This commit also adds a delay when the mouse pointer exits the
tooltip's base anchor or its popover, before hiding it.
* A fade-out animation is layered onto the pointer exit delay to
immediately inform the user that they successfully dismissed the
popover, while still providing a way for them to cancel it if
it was a mistake and they still wanted to interact with it.
* No animation is used for revealing it, because we don't want
people to try to interact with an element while it's in the
middle of fading in: either they're allowed to interact with
it while it's fading in, meaning it can't serve as mistake-
proofing for opening the popover, or they can't, but they
might try and be frustrated.
See also:
* https://www.nngroup.com/articles/timing-exposing-content/
* https://www.nngroup.com/articles/tooltip-guidelines/
* https://bjk5.com/post/44698559168/breaking-down-amazons-mega-dropdown
2023-05-23 17:29:43 -05:00
|
|
|
wait-for-count: (".tooltip.popover", 1)
|
2022-11-07 22:18:01 -06:00
|
|
|
|
2023-05-23 19:19:35 -05:00
|
|
|
assert-css: (
|
|
|
|
"//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']",
|
|
|
|
{"color": |link_color|},
|
|
|
|
ALL,
|
|
|
|
)
|
|
|
|
|
2023-01-06 08:18:51 -06:00
|
|
|
assert-css: (
|
2023-01-26 14:32:33 -06:00
|
|
|
".tooltip.popover h3",
|
2022-11-07 22:18:01 -06:00
|
|
|
{"color": |header_color|},
|
|
|
|
ALL,
|
2023-01-06 08:18:51 -06:00
|
|
|
)
|
|
|
|
assert-css: (
|
2023-01-26 14:32:33 -06:00
|
|
|
".tooltip.popover pre",
|
2022-11-07 22:18:01 -06:00
|
|
|
{"color": |content_color|},
|
|
|
|
ALL,
|
2023-01-06 08:18:51 -06:00
|
|
|
)
|
|
|
|
assert-css: (
|
2023-01-26 14:32:33 -06:00
|
|
|
".tooltip.popover pre a.struct",
|
2022-11-07 22:18:01 -06:00
|
|
|
{"color": |type_color|},
|
|
|
|
ALL,
|
2023-01-06 08:18:51 -06:00
|
|
|
)
|
|
|
|
assert-css: (
|
2023-01-26 14:32:33 -06:00
|
|
|
".tooltip.popover pre a.trait",
|
2022-11-07 22:18:01 -06:00
|
|
|
{"color": |trait_color|},
|
|
|
|
ALL,
|
2023-01-06 08:18:51 -06:00
|
|
|
)
|
|
|
|
},
|
2022-11-07 22:18:01 -06:00
|
|
|
)
|
|
|
|
|
|
|
|
call-function: (
|
|
|
|
"check-colors",
|
|
|
|
{
|
|
|
|
"theme": "ayu",
|
2023-07-02 04:14:31 -05:00
|
|
|
"link_color": "#39afd7",
|
|
|
|
"content_color": "#e6e1cf",
|
|
|
|
"header_color": "#fff",
|
|
|
|
"type_color": "#ffa0a5",
|
|
|
|
"trait_color": "#39afd7",
|
2022-11-07 22:18:01 -06:00
|
|
|
},
|
|
|
|
)
|
|
|
|
|
|
|
|
call-function: (
|
|
|
|
"check-colors",
|
|
|
|
{
|
|
|
|
"theme": "dark",
|
2023-07-02 04:14:31 -05:00
|
|
|
"link_color": "#d2991d",
|
|
|
|
"content_color": "#ddd",
|
|
|
|
"header_color": "#ddd",
|
|
|
|
"type_color": "#2dbfb8",
|
|
|
|
"trait_color": "#b78cf2",
|
2022-11-07 22:18:01 -06:00
|
|
|
},
|
|
|
|
)
|
|
|
|
|
|
|
|
call-function: (
|
|
|
|
"check-colors",
|
|
|
|
{
|
|
|
|
"theme": "light",
|
2023-07-02 04:14:31 -05:00
|
|
|
"link_color": "#3873ad",
|
|
|
|
"content_color": "black",
|
|
|
|
"header_color": "black",
|
|
|
|
"type_color": "#ad378a",
|
|
|
|
"trait_color": "#6e4fc9",
|
2022-11-07 22:18:01 -06:00
|
|
|
},
|
|
|
|
)
|
2022-11-08 18:59:03 -06:00
|
|
|
|
|
|
|
reload:
|
|
|
|
|
|
|
|
// Check that pressing escape works
|
2023-01-26 14:32:33 -06:00
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
move-cursor-to: "//*[@class='tooltip popover']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
2022-11-08 18:59:03 -06:00
|
|
|
press-key: "Escape"
|
2023-01-26 14:32:33 -06:00
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
assert: "#method\.create_an_iterator_from_read .tooltip:focus"
|
2022-11-08 18:59:03 -06:00
|
|
|
|
|
|
|
// Check that clicking outside works.
|
2023-01-26 14:32:33 -06:00
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
2022-11-08 18:59:03 -06:00
|
|
|
click: ".search-input"
|
2023-01-26 14:32:33 -06:00
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
assert-false: "#method\.create_an_iterator_from_read .tooltip:focus"
|
2022-11-08 18:59:03 -06:00
|
|
|
|
|
|
|
// Check that pressing tab over and over works.
|
2023-01-26 14:32:33 -06:00
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
move-cursor-to: "//*[@class='tooltip popover']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
2022-11-08 18:59:03 -06:00
|
|
|
press-key: "Tab"
|
|
|
|
press-key: "Tab"
|
|
|
|
press-key: "Tab"
|
|
|
|
press-key: "Tab"
|
|
|
|
press-key: "Tab"
|
|
|
|
press-key: "Tab"
|
|
|
|
press-key: "Tab"
|
2023-01-26 14:32:33 -06:00
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
assert: "#method\.create_an_iterator_from_read .tooltip:focus"
|
2022-11-18 17:25:37 -06:00
|
|
|
|
2024-04-20 07:53:14 -05:00
|
|
|
define-function: (
|
|
|
|
"setup-popup",
|
|
|
|
[],
|
|
|
|
block {
|
|
|
|
store-window-property: {"scrollY": scroll}
|
|
|
|
click: "#method\.create_an_iterator_from_read .fn"
|
|
|
|
// We ensure that the scroll position changed.
|
|
|
|
assert-window-property-false: {"scrollY": |scroll|}
|
|
|
|
// Store the new position.
|
|
|
|
store-window-property: {"scrollY": scroll}
|
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
wait-for: "//*[@class='tooltip popover']"
|
|
|
|
click: "#settings-menu a"
|
|
|
|
}
|
|
|
|
)
|
|
|
|
|
2022-11-18 17:25:37 -06:00
|
|
|
// Now we check that the focus isn't given back to the wrong item when opening
|
|
|
|
// another popover.
|
2024-04-20 07:53:14 -05:00
|
|
|
call-function: ("setup-popup", {})
|
2022-11-18 17:25:37 -06:00
|
|
|
click: ".search-input"
|
|
|
|
// We ensure we didn't come back to the previous focused item.
|
|
|
|
assert-window-property-false: {"scrollY": |scroll|}
|
|
|
|
|
|
|
|
// Same but with Escape handling.
|
2024-04-20 07:53:14 -05:00
|
|
|
call-function: ("setup-popup", {})
|
2022-11-18 17:25:37 -06:00
|
|
|
press-key: "Escape"
|
|
|
|
// We ensure we didn't come back to the previous focused item.
|
|
|
|
assert-window-property-false: {"scrollY": |scroll|}
|
rustdoc: improve popover focus handling JS
This commit fixes a few inconsistencies and erratic behavior from the
notable traits, settings, and sidebar popups:
* It makes it so that pressing Escape closes the mobile sidebar.
This is a bit difficult to do on iPhone, but on other setups like
desktop tiling window managers, it's easy and makes sense.
* It makes sure that pressing escape while a notable trait popover is
open focuses the popover's toggle button, instead of leaving nothing
focused, since that makes more sense with keyboard navigation. Clicking
the settings, help, or sidebar buttons, however, will not focus the
notable trait popover toggle button.
* It ensures that notable trait and settings popovers are exclusive
with the mobile sidebar. Nothing should ever overlap a popover, and
there should never be more than one popover open at once.
2022-11-26 10:52:58 -06:00
|
|
|
|
|
|
|
// Opening the mobile sidebar should close the popover.
|
2023-04-11 12:11:34 -05:00
|
|
|
set-window-size: (650, 600)
|
2023-01-26 14:32:33 -06:00
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
rustdoc: improve popover focus handling JS
This commit fixes a few inconsistencies and erratic behavior from the
notable traits, settings, and sidebar popups:
* It makes it so that pressing Escape closes the mobile sidebar.
This is a bit difficult to do on iPhone, but on other setups like
desktop tiling window managers, it's easy and makes sense.
* It makes sure that pressing escape while a notable trait popover is
open focuses the popover's toggle button, instead of leaving nothing
focused, since that makes more sense with keyboard navigation. Clicking
the settings, help, or sidebar buttons, however, will not focus the
notable trait popover toggle button.
* It ensures that notable trait and settings popovers are exclusive
with the mobile sidebar. Nothing should ever overlap a popover, and
there should never be more than one popover open at once.
2022-11-26 10:52:58 -06:00
|
|
|
click: ".sidebar-menu-toggle"
|
|
|
|
assert: "//*[@class='sidebar shown']"
|
2023-01-26 14:32:33 -06:00
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
assert-false: "#method\.create_an_iterator_from_read .tooltip:focus"
|
|
|
|
// Clicking a notable trait tooltip popover should close the sidebar.
|
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
rustdoc: improve popover focus handling JS
This commit fixes a few inconsistencies and erratic behavior from the
notable traits, settings, and sidebar popups:
* It makes it so that pressing Escape closes the mobile sidebar.
This is a bit difficult to do on iPhone, but on other setups like
desktop tiling window managers, it's easy and makes sense.
* It makes sure that pressing escape while a notable trait popover is
open focuses the popover's toggle button, instead of leaving nothing
focused, since that makes more sense with keyboard navigation. Clicking
the settings, help, or sidebar buttons, however, will not focus the
notable trait popover toggle button.
* It ensures that notable trait and settings popovers are exclusive
with the mobile sidebar. Nothing should ever overlap a popover, and
there should never be more than one popover open at once.
2022-11-26 10:52:58 -06:00
|
|
|
assert-false: "//*[@class='sidebar shown']"
|
|
|
|
|
rustdoc: redesign toolbar and disclosure widgets
This adds labels to the icons and moves them away from the search box.
These changes are made together, because they work together, but are based on
several complaints:
* The [+/-] thing are a Reddit-ism. They don't look like buttons, but look
like syntax
<https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/More.20visual.20difference.20for.20the.20.2B.2F-.20.20Icons>,
<https://github.com/rust-lang/rust/issues/59851>
(some of these are laundry lists with more suggestions, but they all
mention [+/-] looking wrong)
* The settings, help, and summary buttons are also too hard to recognize
<https://lwn.net/Articles/987070/>,
<https://github.com/rust-lang/rust/issues/90310>,
<https://github.com/rust-lang/rust/issues/14475#issuecomment-274241997>,
<https://internals.rust-lang.org/t/improve-rustdoc-design/12758>
("Not all functionality is self-explanatory, for example the [+] button in
the top right corner, the theme picker or the settings button.")
The toggle-all and toggle-individual buttons both need done at once, since we
want them to look like they go together. This changes them from both being
[+/-] to both being arrows.
Settings and Help are also migrated, so that the whole group can benefit from
being described using actual words.
Additionally, the Help button is only shown on SERPs, not all the time.
This is done for two major reasons:
* Most of what's in there is search-related. The things that aren't are
keyboard commands, and the search box tells you about that anyway.
Pressing <kbd>?</kbd> will temporarily show the button and its popover.
* I'm trading it off by showing the help button, even on mobile.
It's useful since you can use the search engine suggestions there.
* The three buttons were causing line wrapping on too many desktop layouts.
2024-08-25 01:11:30 -05:00
|
|
|
// Also check the focus handling for the settings button.
|
2023-04-11 12:11:34 -05:00
|
|
|
set-window-size: (1100, 600)
|
rustdoc: improve popover focus handling JS
This commit fixes a few inconsistencies and erratic behavior from the
notable traits, settings, and sidebar popups:
* It makes it so that pressing Escape closes the mobile sidebar.
This is a bit difficult to do on iPhone, but on other setups like
desktop tiling window managers, it's easy and makes sense.
* It makes sure that pressing escape while a notable trait popover is
open focuses the popover's toggle button, instead of leaving nothing
focused, since that makes more sense with keyboard navigation. Clicking
the settings, help, or sidebar buttons, however, will not focus the
notable trait popover toggle button.
* It ensures that notable trait and settings popovers are exclusive
with the mobile sidebar. Nothing should ever overlap a popover, and
there should never be more than one popover open at once.
2022-11-26 10:52:58 -06:00
|
|
|
reload:
|
2023-01-26 14:32:33 -06:00
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
click: "//*[@id='method.create_an_iterator_from_read']//*[@class='tooltip']"
|
|
|
|
assert-count: ("//*[@class='tooltip popover']", 1)
|
rustdoc: redesign toolbar and disclosure widgets
This adds labels to the icons and moves them away from the search box.
These changes are made together, because they work together, but are based on
several complaints:
* The [+/-] thing are a Reddit-ism. They don't look like buttons, but look
like syntax
<https://rust-lang.zulipchat.com/#narrow/stream/266220-t-rustdoc/topic/More.20visual.20difference.20for.20the.20.2B.2F-.20.20Icons>,
<https://github.com/rust-lang/rust/issues/59851>
(some of these are laundry lists with more suggestions, but they all
mention [+/-] looking wrong)
* The settings, help, and summary buttons are also too hard to recognize
<https://lwn.net/Articles/987070/>,
<https://github.com/rust-lang/rust/issues/90310>,
<https://github.com/rust-lang/rust/issues/14475#issuecomment-274241997>,
<https://internals.rust-lang.org/t/improve-rustdoc-design/12758>
("Not all functionality is self-explanatory, for example the [+] button in
the top right corner, the theme picker or the settings button.")
The toggle-all and toggle-individual buttons both need done at once, since we
want them to look like they go together. This changes them from both being
[+/-] to both being arrows.
Settings and Help are also migrated, so that the whole group can benefit from
being described using actual words.
Additionally, the Help button is only shown on SERPs, not all the time.
This is done for two major reasons:
* Most of what's in there is search-related. The things that aren't are
keyboard commands, and the search box tells you about that anyway.
Pressing <kbd>?</kbd> will temporarily show the button and its popover.
* I'm trading it off by showing the help button, even on mobile.
It's useful since you can use the search engine suggestions there.
* The three buttons were causing line wrapping on too many desktop layouts.
2024-08-25 01:11:30 -05:00
|
|
|
click: "#settings-menu a"
|
|
|
|
wait-for: "#settings"
|
2023-01-26 14:32:33 -06:00
|
|
|
assert-count: ("//*[@class='tooltip popover']", 0)
|
|
|
|
assert-false: "#method\.create_an_iterator_from_read .tooltip:focus"
|