Merge branch 'main' into selecticons

Author: josepharhar

css-anchor-position-1/Overview.bs

@@ -10,6 +10,7 @@ Editor: Bert Bos, W3C, bert@w3.org, w3cid 3343
 Editor: Elika J. Etemad / fantasai, Apple, http://fantasai.inkedblade.net/contact, w3cid 35400
 Editor: Lea Verou, Invited Expert, http://lea.verou.me/about/, w3cid 52258
 Editor: Sebastian Zartner, Invited Expert, sebastianzartner@gmail.com, w3cid 64937
+Editor: Noam Rosenthal, Google, w3cid 121539
 Abstract: This module contains the features of CSS relating to the borders and decorations of boxes on the page.
 Ignored Terms: total width
 Warning: Not Ready

css-borders-4/Overview.bs

@@ -3,9 +3,8 @@ Title: CSS Conditional Rules Module Level 3
 Group: csswg
 Shortname: css-conditional
 Level: 3
-Status: CRD
-Prepare for TR: yes
-Date: 2024-08-15
+Status: ED
+Prepare for TR: no
 Work Status: Testing
 Implementation Report: https://test.csswg.org/harness/results/css-conditional-3_dev/grouped/
 Implementation Report: https://wpt.fyi/results/css/css-conditional?label=master&label=experimental&aligned

css-conditional-3/Overview.bs

@@ -43,6 +43,7 @@ Default Highlight: css
 	spec:css-contain-2; type:dfn; text:layout containment box
 	spec:css-contain-2; type:dfn; text:size containment box
 	spec:css-pseudo-4; type:dfn; text:fictional tag sequence
+	spec:css-scroll-snap-2; type:dfn; text:scrollsnapchanging
 	spec:css-sizing-4; type:property; text:contain-intrinsic-size
 	spec:css-sizing-4; type:property; text:aspect-ratio
 	spec:intersection-observer; type:dfn; text:intersection root
@@ -878,7 +879,7 @@ Size Container Features</h3>
 	allows querying
 	the size of the [=query container=]’s [=principal box=].
 	It is a boolean combination of
-	individual <dfn>size features</dfn> (<<size-feature>>)
+	individual <dfn export>size features</dfn> (<<size-feature>>)
 	that each query a single, specific dimensional feature of the [=query container=].
 	The syntax of a <dfn><<size-feature>></dfn> is the same as for a [=media feature=]:
 	a feature name, a comparator, and a value.
@@ -1195,7 +1196,8 @@ Scroll snapping: the '@container/snapped' feature</h4>
 	</pre>
 
 	The '@container/snapped' [=container feature=] queries whether a [=snap target=]
-	is snapped to its [=snap container=] in the given axis.
+	is, or would be, snapped to its [=snap container=], in the given axis. That is,
+	it matches any [=snap target=] that the {{scrollsnapchanging}} event is fired for.
 
 	<dl dfn-type=value dfn-for="@container/snapped">
 		<dt><dfn>none</dfn>

css-conditional-5/Overview.bs

@@ -4060,13 +4060,13 @@ UAs may alternatively choose
 to not initially expose any user-installed fonts to aid privacy on the web;
 for the set of installed fonts a user has installed
 is often used as a tracking vector to track users across the web.
-Users would then add to add to or remove fonts from that set,
+Users should then be able to add to or remove fonts from that set,
 according to their needs.
 
 UAs may choose a hybrid approach, where some user-installed fonts
 are initially exposed for internationalization,
 but others aren't.
-Again, users would be able to customise this starting set.
+Again, users should be able to customise this starting set.
 
 UAs are expected to make informed decisions
 on which fonts they expose to the web by default,

css-fonts-4/Overview.bs

@@ -11,6 +11,51 @@ Abstract: This document is currently a loosely-structured set of ideas and inspi
 Warning: not ready
 </pre>
 
+New Pseudo-Elements {#pseudos}
+==============================
+
+This section defines some pseudo-elements for styling parts of form elements.
+
+<h3 id="picker-pseudo">
+Styling form control pickers: the ''::picker()'' pseudo-element</h3>
+
+  The <dfn>::picker()</dfn> pseudo-element targets the popup picker of form
+  control elements which have popup pickers, such as the <{select}> element. It
+  is an [=element-backed pseudo-element=].
+
+  <pre class=prod>
+    ::picker() = ::picker( <<ident>>+ )
+  </pre>
+
+  Note: Once all of the controls that might support picker styling have it,
+  then we might add a (no-argument) ''::picker'' pseudo-element as well.
+
+  The ''::picker()'' pseudo-element only matches when the <a>originating
+  element</a> supports <a>base appearance</a> and has a popup picker. The
+  specified <<ident>> must also match the <dfn>unique picker name</dfn> of the
+  <a>originating element</a>. For example, the <a>unique picker name</a> for
+  the <{select}> element is "select".
+
+  Since it is an [=element-backed pseudo-element=], There is no restriction on which
+  properties apply to the ''::picker()'' pseudo-element.
+
+  In order for the ''::picker()'' pseudo-element to be rendered, it and its
+  <a>originating element</a> must be rendered with <a>base appearance</a> by
+  applying ''appearance: base'' to both of them.
+
+  <pre class="example">
+&lt;style>
+  select, select::picker(select) {
+    appearance: base;
+  }
+  select::picker(select) {
+    border: 5px solid red;
+    background-color: blue;
+  }
+&lt;/style>
+  </pre>
+
+
 Basic Styling Proposals {#ideas}
 ================================
 

css-forms-1/Overview.bs

@@ -5554,7 +5554,7 @@ Changes since the
 	for previous changes.
 
 <h3 id="changes-2">
-Additions Since Level 2</h3>
+Additions Since Level 1</h3>
 
 	The following features have been added since
 	<a href="http://www.w3.org/TR/css-grid-1/">Level 1</a>:

css-grid-2/Overview.bs

@@ -2,9 +2,7 @@
 Title: CSS Grid Layout Module Level 3
 Shortname: css-grid
 Level: 3
-Status: FPWD
-Prepare for TR: yes
-Date: 2024-09-19
+Status: ED
 Work Status: Exploring
 Group: csswg
 TR:  https://www.w3.org/TR/css-grid-3/
@@ -677,6 +675,10 @@ Masonry Track Specification</h3>
 <h4 id=masonry-intrinsic-repeat>
 Intrinsic Tracks and repeat()</h4>
 
+	ISSUE(10915): Should we allow auto-repeated content-based tracks?
+	Is this a reasonable definition for them?
+	Should they work also in Grid Layout somehow?
+
 	In Grid Layout,
 	all [=grid items=] are placed in the grid
 	<em>before</em> the grid tracks are sized.
@@ -862,18 +864,20 @@ repeat(auto-areas)</h3>
 	the final repetition is truncated as necessary
 	to produce the correct number of tracks.
 
-	Note: Unlike ''repeat()/auto-fill''--
+	Note: Unlike ''repeat()/auto-fit''--
 	which always repeats at least once and always repeats the track listing entirely--
 	the number of repetitions for ''repeat()/auto-areas'' can be zero
 	(if there are already enough explicit tracks),
 	and the final repetition can be partial.
 
 	If 'grid-template-areas' / 'masonry-template-areas' is ''grid-template-areas/none'',
-	this value behaves as ''auto-fill''.
+	this value behaves as ''auto-fit''.
 
 	Note: This value applies both to regular [=grid containers=] and to [=masonry containers=].
 
 	ISSUE(10854): It's unclear if we actually need this value.
+	Note that the explicit grid already takes values from 'grid-auto-columns'/'grid-auto-rows'/'masonry-auto-tracks'
+	as needed to match the number of template areas.
 
 <h4 id="repeat-auto-fit">
 repeat(auto-fit)</h3>
@@ -1421,31 +1425,6 @@ Absolute Positioning</h2>
 	Maybe it could defined as the max (or min?) current [=running position=]
 	of the [=grid-axis=] tracks at that point?  Or the end of the item before it?
 
-<h2 id="performance-notes">
-Performance Notes</h2>
-
-	In general, masonry layout should have significantly better performance
-	than the equivalent regular (2-axis) grid layout,
-	particularly when the [=stacking axis=] is the [=block axis=]
-	since the intrinsic sizing of grid rows is typically quite expensive.
-	Any intrinsic track sizing in the [=grid axis=] should be cheaper too,
-	because, typically, only a subset of items contribute to the intrinsic sizing in a masonry layout,
-	contrary to a 2-axis grid where all items spanning an intrinsically-sized track contribute.
-	Stretched items do a second layout with the new size (when it actually changed)
-	so this can be costly if there are a huge amount of stretched items
-	that each contains a lot of content.
-	Especially nested stretched masonry layouts should be avoided
-	unless they are small/trivial.
-
-	Advisement: This can be ameliorated by the author
-	by opting out from the stretching on most items though,
-	e.g. specifying ''justify/align-items:start''
-	and then opting in for just a few items with ''justify/align-self:stretch''
-	to let those items fill the [=stacking axis=].
-	(This performance analysis is from a Gecko perspective,
-	but I suspect there's some truth to it for other layout engines as well.)
-
-
 <h2 id="graceful-degradation">
 Graceful Degradation</h2>
 
@@ -1478,25 +1457,49 @@ Graceful Degradation</h2>
 Acknowledgements</h2>
 
 	Thanks goes to Cameron McCormack who wrote a masonry layout explainer document
-	(from which I lifted the Background chapter) and presented it to the CSSWG.
+	(from which was lifted the Background chapter) and presented it to the CSSWG,
+	and to Mats Palmgren who developed the original version of this specification.
 	Thanks also to everyone who provided feedback on the <a href="https://github.com/w3c/csswg-drafts/issues/4650">initial proposal</a> for this feature.
 
 <h2 id=security>
 Security Considerations</h2>
 
-	<p>
 	As a layout specification,
 	this spec introduces no new security considerations
 	beyond that exposed by CSS layout in general.
-	</p>
 
 <h2 id=privacy>
 Privacy Considerations</h2>
 
-	<p>
 	As a layout specification,
 	this spec introduces no new privacy considerations
 	beyond that exposed by CSS layout in general.
-	</p>
 
-<wpt-rest></wpt-rest>
+<h2 class="no-num" id="changes">
+Changes</h2>
+
+
+<h3 id="changes-3">
+Additions Since Level 2</h3>
+
+	The following features have been added since
+	<a href="http://www.w3.org/TR/css-grid-2/">Level 2</a>:
+
+	<ul>
+		<li>Added [=masonry layout=].
+		<li>Added ''*-reverse'' keywords to 'grid-auto-flow'.
+	</ul>
+
+<h3 class="no-num" id="recent-changes">
+Recent Changes</h3>
+
+	The following changes have been made since the
+	<a href='https://www.w3.org/TR/2024/WD-css-grid-3-20240919/'>First Public Working Draft</a>:
+
+	* Drafted ability to mix ''auto-fill''/''auto-fit'' ''repeat()'' values with content-based track sizes
+		in the [=grid-independent option=] and made it the initial behavior 'masonry-template-tracks'.
+		(Issues <a href="https://github.com/w3c/csswg-drafts/issues/10915">10915</a>,
+		and <a href="https://github.com/w3c/csswg-drafts/issues/10869">10869</a>)
+	* Added ''masonry-slack: infinite''.
+		(<a href="https://github.com/w3c/csswg-drafts/issues/10883">Issue 10883</a>)
+	* Minor corrections, updated acknowledgements, and added an example.

css-grid-3/Overview.bs

@@ -141,7 +141,7 @@ Setting up Custom Highlights</h2>
 <h3 id=creation>
 Creating Custom Highlights</h3>
 
-	A <dfn>custom highlight</dfn> is a collection of [=ranges=]
+	A <dfn export>custom highlight</dfn> is a collection of [=ranges=]
 	representing portions of a document.
 	They do not necessarily fit into the element tree,
 	and can arbitrarily cross element boundaries without honoring its nesting structure.
@@ -246,7 +246,7 @@ Registering Custom Highlights</h3>
 		the passed-in [=custom highlight name=] as <var ignore>keyArg</var>,
 		and the passed-in highlight as <var ignore>valueArg</var>.
 
-		The <dfn>custom highlight name</dfn> assigned to a [=custom highlight=] when it is [=registered=]
+		The <dfn export>custom highlight name</dfn> assigned to a [=custom highlight=] when it is [=registered=]
 		is used to identify the highlight during styling (see [[#styling-highlights]]).
 
 	Note: When registering a [=custom highlight=],
@@ -304,15 +304,12 @@ Styling Custom Highlights</h2>
 <h3 id=custom-highlight-pseudo>
 The Custom Highlight Pseudo-element: ''::highlight()''</h3>
 
-	The <dfn>::highlight(<<custom-highlight-name>>)</dfn> pseudo-element
+	The ''::highlight()'' pseudo-element
 	(also known as the <dfn>custom highlight pseudo-element</dfn>)
 	represents the portion of a document that
 	is being [=contained=] or [=partially contained=]
 	in all the [=ranges=] of the [=registered=] [=custom highlight=]
-	with the [=custom highlight name=] <<custom-highlight-name>>,
-	if any.
-	<dfn type><<custom-highlight-name>></dfn> must be a valid CSS <<ident-token>>.
-
+	with the [=custom highlight name=] specified as its argument.
 
 <h3 id=processing-model>
 Processing Model</h3>

css-highlight-api-1/Overview.bs

@@ -1027,7 +1027,7 @@ Nesting Selector: the ''&'' selector {#nest-selector}
 
 		<pre class=lang-css>
 		.a1, .a2, .a3 {
-			.b1, .b3, .b3 {
+			.b1, .b2, .b3 {
 				.c1, .c2, .c3 {
 					...;
 				}