-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open impl blocks by default #84552
Open impl blocks by default #84552
Changes from 5 commits
33a7098
bcad1ec
175cd9b
1afea79
9b44c4b
6c8969c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
// This test ensures that the element corresponding to the hash is displayed. | ||
goto: file://|DOC_PATH|/struct.Foo.html#method.borrow | ||
// In the blanket implementations list, "Borrow" is the second one, hence the ":nth(2)". | ||
assert: ("#blanket-implementations-list > details:nth-child(2)", "open", "") | ||
// Please note the "\" below is needed because otherwise ".borrow" would be interpreted as | ||
// a class selector. | ||
assert: ("#method\.borrow", {"display": "flex"}) | ||
// We first check that the impl block is open by default. | ||
assert: ("#implementations + details", "open", "") | ||
// We collapse it. | ||
click: "#implementations + details > summary" | ||
// We check that it was collapsed as expected. | ||
assert-false: ("#implementations + details", "open", "") | ||
// To ensure that we will click on the currently hidden method. | ||
assert: (".sidebar-links > a", "must_use") | ||
click: ".sidebar-links > a" | ||
// We check that the impl block was opened as expected so that we can see the method. | ||
assert: ("#implementations + details", "open", "") |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
// This test ensures that the impl blocks are open by default. | ||
goto: file://|DOC_PATH|/struct.Foo.html | ||
assert: ("#main > details.implementors-toggle", "open", "") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you add a test that intentionally fails to make sure this runs at all? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They are not run, that's for sure. Otherwise, it'd have failed a long time ago because of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok. In the meantime, can you run it locally and make sure it passes? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This version didn't because I forgot to commit the one with the correct URL ( There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you fix it to have the correct URL? I don't see the point of adding a test we know will fail. While you're at it, can you update the other test to pass instead of removing it altogether? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Look at my comment below. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The test which fails checked for attributes toggles. Since they don't have toggles anymore, there is no point of keeping the test. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Can you instead test that it doesn't have toggles? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it be useful to check that something was removed? For example, if we put back toggles on attributes with a different DOM, the test would still be happy. Which is why it's simpler to enforce what exists over what doesn't. (Not sure if that makes sense said like this ><) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree with @GuillaumeGomez. When removing "code that does X," it's often tempting to add a test for "doesn't do X anymore." But the problem is there are a zillion ways it could wind up doing X again, and it's impossible to cover all of them (or even a reasonable fraction). It winds up adding to the test running time, and the burden of maintaining tests, without a corresponding benefit. |
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I understand it, we hide things during load because we're going to manipulate their DOM, and DOM manipulation on hidden things goes faster. The main DOM manipulation is adding the
[+]
toggles. When we fully switch over to<details>
we won't need to hide portions of the DOM during load anymore.I'd like to start doing that as we go. Rather than opening the
<details>
tags on load, we should set them to the global default in our generated HTML, and on load we should hide or show them according to settings.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not all details should be opened by details. For example the traits implementations blocks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or did you mean that we should generate the
<details>
with "open" directly? Still: we will need this JS in any case for when we press the global toggle.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I mean that for default-shown sections we should generate
<details open>
.I agree we need JS to make
<details>
respond to the global toggle, but I believe that's already in place. And it wouldn't be in this chunk of code, which executes on load rather than in response to the global toggle.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, I'll modify it then.