Michael Howell
Michael Howell
@bors r=GuillaumeGomez
No complaints, other than keeping the issue open because this is, unfortunately, an *incomplete* solution. It doesn't help unless the Develop menu is turned on. @bors r+ rollup
> Do you have a more general workaround in mind? I was thinking of integrating a small HTTP server into Rustdoc[^why]. That would definitely solve this problem, along with a...
> Could you add a rustdoc-js test for it Sure, the second commit now adds that. > also add a time limit to ensure it doesn't take more than 10...
I don't think using setTimeout in Node will work, because the search will block the event loop and prevent the timer from actually firing. Doing it in a follow-up PR...
That still sounds like you're thinking of implementing the timeout in Node. Since search.js doesn't explicitly yield to the event loop (and, even if it did, we wouldn't want to...
@craterbot run name=pr-121659-bump-pulldown-cmark mode=rustdoc
@craterbot run name=pr-121659-bump-pulldown-cmark mode=rustdoc start=master#ef324565d071c6d7e2477a195648549e33d6a465 end=try#223112bf1ca31911a6475910c77b36bfa127d5f8
Roughly categorizing what I'm seeing here. The specific crates are in [this Gist](https://gist.github.com/notriddle/8d1859a17e606b004e91d57fee6d7f15): ## (P)roblems: docs that are broken by this change ### P1: unintended strikethrough https://github.com/pulldown-cmark/pulldown-cmark/pull/648 allows `abso~fricking~lutely` to...