mirror of
https://github.com/servo/servo.git
synced 2025-06-06 16:45:39 +00:00
Fix rustdoc warnings in components/layout_2020
(#31587)
* fix rustdoc warnings in components/layout_2020 Signed-off-by: Sandeep Pillai <sandeeppillai@Sandeeps-MacBook-Air.local> * made suggested changes Signed-off-by: Sandeep Pillai <sandeeppillai@Sandeeps-MacBook-Air.local> --------- Signed-off-by: Sandeep Pillai <sandeeppillai@Sandeeps-MacBook-Air.local> Co-authored-by: Sandeep Pillai <sandeeppillai@Sandeeps-MacBook-Air.local>
This commit is contained in:
parent
48f9db9bc5
commit
81e6bd962b
2 changed files with 3 additions and 3 deletions
|
@ -1372,7 +1372,7 @@ fn solve_block_margins_for_in_flow_block_level(pbm: &PaddingBorderMargin) -> (Le
|
|||
}
|
||||
|
||||
/// This is supposed to handle 'justify-self', but no browser supports it on block boxes.
|
||||
/// Instead, <center> and <div align> are implemented via internal 'text-align' values.
|
||||
/// Instead, `<center>` and `<div align>` are implemented via internal 'text-align' values.
|
||||
/// The provided free space should already take margins into account. In particular,
|
||||
/// it should be zero if there is an auto margin.
|
||||
/// <https://drafts.csswg.org/css-align/#justify-block>
|
||||
|
|
|
@ -36,7 +36,7 @@ const XI_LINE_BREAKING_CLASS_ZW: u8 = 28;
|
|||
const XI_LINE_BREAKING_CLASS_WJ: u8 = 30;
|
||||
const XI_LINE_BREAKING_CLASS_ZWJ: u8 = 40;
|
||||
|
||||
/// https://www.w3.org/TR/css-display-3/#css-text-run
|
||||
/// <https://www.w3.org/TR/css-display-3/#css-text-run>
|
||||
#[derive(Debug, Serialize)]
|
||||
pub(crate) struct TextRun {
|
||||
pub base_fragment_info: BaseFragmentInfo,
|
||||
|
@ -450,7 +450,7 @@ impl TextRun {
|
|||
/// Whether or not this character will rpevent a soft wrap opportunity when it
|
||||
/// comes before or after an atomic inline element.
|
||||
///
|
||||
/// From https://www.w3.org/TR/css-text-3/#line-break-details:
|
||||
/// From <https://www.w3.org/TR/css-text-3/#line-break-details>:
|
||||
///
|
||||
/// > For Web-compatibility there is a soft wrap opportunity before and after each
|
||||
/// > replaced element or other atomic inline, even when adjacent to a character that
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue