ade7ecf909
This is shorter, avoids potential conflicts with a crate named `implementors`[^1], and will be less confusing when JS include files are added for type aliases. [^1]: AFAIK, this couldn't actually cause any problems right now, but it's simpler just to make it impossible than relying on never having a file named `trait.Foo.js` in the crate data area.
14 lines
716 B
Plaintext
14 lines
716 B
Plaintext
// This test checks that there are margins applied to methods with no docblocks.
|
|
|
|
// We need to disable this check because `trait.impl/test_docs/trait.TraitWithNoDocblock.js`
|
|
// doesn't exist.
|
|
fail-on-request-error: false
|
|
|
|
go-to: "file://" + |DOC_PATH| + "/test_docs/trait.TraitWithNoDocblocks.html"
|
|
// Check that the two methods are more than 24px apart.
|
|
compare-elements-position-near-false: ("//*[@id='tymethod.first_fn']", "//*[@id='tymethod.second_fn']", {"y": 24})
|
|
|
|
go-to: "file://" + |DOC_PATH| + "/test_docs/struct.TypeWithNoDocblocks.html"
|
|
// Check that the two methods are more than 24px apart.
|
|
compare-elements-position-near-false: ("//*[@id='method.first_fn']", "//*[@id='method.second_fn']", {"y": 24})
|