about summary refs log tree commit diff
path: root/src/test/rustdoc/const-display.rs
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-86/+0
2022-08-13Update `@!has` name in testsNoah Lev-3/+3
2022-03-31Adjust feature names that disagree on const stabilization versionDavid Tolnay-3/+3
2022-02-02Emit valid HTML from rustdocJacob Hoffman-Andrews-3/+3
Previously, tidy-html5 (`tidy`) would complain about a few things in our HTML. The main thing is that `<summary>` tags can't contain `<div>`s. That's easily fixed by changing out the `<div>`s for `<span>`s with `display: block`. However, there's also a rule that `<span>`s can't contain heading elements. `<span>` permits only "phrasing content" https://developer.mozilla.org/en-US/docs/Web/HTML/Element/span, and `<h3>` (and friends) are "Flow content, heading content, palpable content". https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements We have a wrapping `<div>` that goes around each `<h3>`/`<h4>`, etc. We turn that into a `<section>` rather than a `<span>` because `<section>` permits "flow content". https://developer.mozilla.org/en-US/docs/Web/HTML/Element/section After this change we get only three warnings from tidy, run on struct.String.html: line 6 column 10790 - Warning: trimming empty <span> line 1 column 1118 - Warning: <link> proprietary attribute "disabled" line 1 column 1193 - Warning: <link> proprietary attribute "disabled" The empty `<span>` is a known issue - there's a span in front of the search box to work around a strange Safari issue. The `<link>` attributes are the non-default stylesheets. We can probably refactor theme application to avoid using this proprietary "disabled" attribute.
2022-01-13rustdoc: decouple stability and const-stabilityAndy Russell-0/+17
2021-07-25Rustdoc accessibility: use real headers for doc itemsbors-3/+3
Part of #87059 Partially reverts #84703 Preview at: https://notriddle.com/notriddle-rustdoc-test/real-headers/std/index.html
2021-06-21Readd `unsafe` keyword in testsDeadbeef-6/+6
2021-06-21Removed/Updated some cases and simplified `match`Deadbeef-28/+3
2021-06-21Added some tests for `unsafe` in const-dispay.rsDeadbeef-6/+47
2021-06-21Check for const_unstable before printing `const`Deadbeef-4/+4
2021-06-20"(const: unstable)" for stable-but-const-unstableDeadbeef-0/+2
2021-06-01Replace h3 and h4 containing invalid DOMGuillaume Gomez-2/+2
2021-04-03Remove redundant `ignore-tidy-linelength` annotationsSimon Jakobi-2/+0
This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed.
2020-11-29Add support for stable-const-since in docs on items (standalone or assoc)Rune Tynan-0/+10
2020-09-12Fix `const-display.rs` XPATH queries (#1)SlightlyOutOfPhase-3/+3
* Fix `const-display.rs` XPATH queries * Add `issue_76501.rs` test file * Rename issue_76501.rs to issue-76501.rs
2020-08-10Add test for rustc_const_unstable on methodsGuillaume Gomez-0/+9
2019-12-21Require issue = "none" over issue = "0" in unstable attributesRoss MacArthur-4/+4
2019-12-13Fix rustdoc testOliver Scherer-2/+4
2019-12-13Reuse the `staged_api` feature for `rustc_const_unstable`Oliver Scherer-1/+1
2018-12-25Remove licensesMark Rousskov-10/+0
2018-12-23stabilize min_const_unsafe_fn in 1.33.Mazdak Farrokhzad-1/+0
2018-12-19Set constness correctlyGuillaume Gomez-4/+4
2018-12-18Don't render const keyword on stableGuillaume Gomez-0/+43