-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Reapply: Move hiding of boring lines into static content (#846) #1065
Conversation
1eb4884
to
c92e1ea
Compare
@benediktwerner This appears to have broken hidden line removal in some cases. Do you think you can take a look for a fix? Here are some examples: |
@ehuss Sure, although I didn't create the original PR I just took a quick look at it and created #1088 which I think fixes the issue in the first link. The issue in the second link is that the code block is marked with I'm not sure what the best fix for this would be. Is it even correct that code blocks like that aren't converted to a playpen? According to the documentation |
I think it is correct that Would it work to process all |
The thing is So I think the example in the link should be displayed in a playpen and if some code is not runnable it should use |
Also, the |
I see what you're saying that there is not a strong reason for I think |
I actually do think there might be reasons to have hidden lines in In any case, I now changed my PR to always hide lines as long as the language is |
…) (rust-lang#1065) * Move hiding of boring lines into static content (rust-lang#846) * Fix test for hidden code
Was reverted because of formatting in #1064