Uh oh!
There was an error while loading. Please reload this page.
Fix more <a> color - #91179
Conversation
rust-highfive
commented
Nov 24, 2021
Some changes occurred in HTML/CSS/JS. |
There was a problem hiding this comment.
This was originally missing, meaning that the colors weren't computed. I'll add a failure in browser-ui-test directly.
There was a problem hiding this comment.
Therefore this color was updated as well (it's for a struct so not black contrary to the other members of the import).
This comment has been minimized.
This comment has been minimized.
jsha
commented
Nov 24, 2021
Thanks for the fix! @bors r+ |
bors
commented
Nov 24, 2021
📌 Commit 0ba92fe has been approved by |
Fix more <a> color Fixesrust-lang#91175. Another bug I saw is:  I fixed it as well. r? `@jsha`
jsha
commented
Nov 24, 2021
Per #91196 it looks like we also need a rule for |
camelid
commented
Nov 24, 2021
This PR is already in a rollup, so a separate PR is probably best. |
GuillaumeGomez
commented
Nov 24, 2021
Also please open an issue so we can keep track of things more easily. |
camelid
commented
Nov 24, 2021
There's already #91196...? |
GuillaumeGomez
commented
Nov 24, 2021
Indeed... Sorry, tired. Please ignore my comment. |
Fix more <a> color Fixesrust-lang#91175. Another bug I saw is:  I fixed it as well. r? `@jsha`
…laumeGomez Rollup of 7 pull requests Successful merges: - rust-lang#89542 (Partially stabilize `duration_consts_2`) - rust-lang#90044 (Restrict aarch64 outline atomics to glibc for now.) - rust-lang#90420 (Create rustdoc_internals feature gate) - rust-lang#91075 (Reduce prominence of item-infos) - rust-lang#91151 (Fix test in std::process on android) - rust-lang#91179 (Fix more <a> color) - rust-lang#91199 (rustdoc: Add test for mixing doc comments and attrs) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
jsha
commented
Nov 25, 2021
It turns out |
…ci, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc `@jyn514` r? `@jsha`
…ci, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc ``@jyn514`` r? ``@jsha``
…ci, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc ```@jyn514``` r? ```@jsha```
…, r=jsha Improve rustdoc-gui CI As commented [here](rust-lang#91179 (comment)): When the text isn't displayed, the color returned by puppeteer is always `rgba(0,0,0,0)`, which is definitely not the right value. To prevent this error from happening again, `browser-ui-test` will now fail if a CSS color check is run when the text isn't displayed. Either this PR or rust-lang#91179 is merged first, they'll conflict because I made changes to the same test file. cc `@jyn514` r? `@jsha`
Fixes#91175.
Another bug I saw is:
I fixed it as well.
r? @jsha