From 2964f336f59820d0ec50ffec63a40a499d0d1535 Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Mon, 8 Feb 2021 16:14:00 -0500 Subject: [PATCH 1/2] [css-fonts-4] HTML validation from Bikeshed - Drop old summary attribute from table - Trailing paragraphs in OLs - Nested links --- css-fonts-4/Overview.bs | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/css-fonts-4/Overview.bs b/css-fonts-4/Overview.bs index a8ddb119059c..16cfc0d769b1 100644 --- a/css-fonts-4/Overview.bs +++ b/css-fonts-4/Overview.bs @@ -582,7 +582,7 @@ Relative Weights The computed weight is calculated based on the inherited 'font-weight!!property' value using the chart below. - +
Inherited value (w) @@ -3272,15 +3272,15 @@ if all font style properties were set to their initial value. are checked in this stage. 5. If no match is found, oblique values less than or equal to 0deg are checked in descending order until a match is found. 6. If no match is found, italic values less than or equal to 0 are checked in descending order until a match is found. + -
- Similar to the previous example, here is the conceptual distance graph for an element styled with "font-style: oblique 13deg": +
+ Similar to the previous example, here is the conceptual distance graph for an element styled with "font-style: oblique 13deg": - distance graph + distance graph - As you can see, because font D contains the minimum oblique value across the entire family, font D would be selected by this algorithm. However, if font D were somehow eliminated from the family, font C would then contain the lowest distance in the family, so it would be selected. If C were eliminated, E would be selected. If E were eliminated, font B would not be chosen immediately; instead, italic values would be consulted and an italic value might be chosen. However, if no italic value is chosen, font B would then be selected, followed by font A. -
- + As you can see, because font D contains the minimum oblique value across the entire family, font D would be selected by this algorithm. However, if font D were somehow eliminated from the family, font C would then contain the lowest distance in the family, so it would be selected. If C were eliminated, E would be selected. If E were eliminated, font B would not be chosen immediately; instead, italic values would be consulted and an italic value might be chosen. However, if no italic value is chosen, font B would then be selected, followed by font A. +
If the value of 'font-style!!property' is ''oblique'' and the requested angle is less than 0deg and greater than -20deg, follow the steps above, except with the negated values and opposite directions. If the value of 'font-style!!property' is ''oblique'' and the requested angle is less than or equal to -20deg, follow the steps above, except with the negated values and opposite directions. @@ -3373,14 +3373,14 @@ if all font style properties were set to their initial value. computations, e.g., by ''em'' values in other properties, are based on the 'font-size' value that is used, not the one that is specified. - - Note that more than one font might be remaining in the matching set after performing - the above steps. If so, the user agent must choose a single font from - the matching set and continue these steps with it. The choice of which - font to choose can differ between multiple user agents and multiple operating - system platforms; however, it must not differ between two elements in the same document. + Note that more than one font might be remaining in the matching set after performing + the above steps. If so, the user agent must choose a single font from + the matching set and continue these steps with it. The choice of which + font to choose can differ between multiple user agents and multiple operating + system platforms; however, it must not differ between two elements in the same document. + 5. If the matched face is defined via ''@font-face'' rules, user agents must use the procedure below to select a single font: @@ -6585,7 +6585,7 @@ None.

How does this specification distinguish between behavior in first-party and third-party contexts?

For font loads, user agents must use the -potentially CORS-enabled fetch method defined by the [[!HTML]] specification +potentially CORS-enabled fetch method defined by the [HTML] specification for URL’s defined within @font-face rules. When fetching, user agents must use "Anonymous" mode, set the referrer source to the stylesheet’s URL From c2825b06d1e754808bb4ed10a5f309fae33b9df4 Mon Sep 17 00:00:00 2001 From: Tab Atkins Jr Date: Tue, 9 Feb 2021 07:57:49 -0800 Subject: [PATCH 2/2] Restore biblio link, restrict surrounding link to not overlap --- css-fonts-4/Overview.bs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/css-fonts-4/Overview.bs b/css-fonts-4/Overview.bs index 16cfc0d769b1..138560f04fa6 100644 --- a/css-fonts-4/Overview.bs +++ b/css-fonts-4/Overview.bs @@ -6584,12 +6584,12 @@ None.

How does this specification distinguish between behavior in first-party and third-party contexts?

-For font loads, user agents must use the -potentially CORS-enabled fetch method defined by the [HTML] specification +For font loads, user agents must use the +potentially CORS-enabled fetch method defined by the [[!HTML]] specification for URL’s defined within @font-face rules. When fetching, user agents must use "Anonymous" mode, set the referrer source to the stylesheet’s URL -and set the origin to the URL of the containing document. +and set the origin to the URL of the containing document. Thus, fonts will typically not be loaded cross-origin unless authors specifically takes steps to permit cross-origin loads.