Remove unnecessary comments

Author: aaronrobertshaw

lib/class-wp-theme-json-gutenberg.php

@@ -2429,7 +2429,6 @@ private static function get_block_nodes( $theme_json, $selectors = array() ) {
 			$variation_selectors = array();
 			$variation_nodes     = array();
 
-			// TODO: Should we be supporting recursive variations and block type styles?
 			foreach ( $variations as $variation => $variation_node ) {
 				$variation_selector    = $selectors[ $name ]['styleVariations'][ $variation ];
 				$variation_selectors[] = array(
@@ -2469,10 +2468,6 @@ private static function get_block_nodes( $theme_json, $selectors = array() ) {
 				}
 
 				foreach ( $variation_elements as $variation_element => $variation_element_node ) {
-					// TODO: See if there is a way to clean up the generation of element selectors.
-					// The following code varies from standard block element selectors only to avoid
-					// that the $selectors[ $name ]['elements'][ $variation_element ] value would
-					// nest the block's root selector.
 					$nodes[] = array(
 						'path'     => array( 'styles', 'blocks', $name, 'variations', $variation, 'elements', $variation_element ),
 						'selector' => static::scope_selector( $variation_selector, static::ELEMENTS[ $variation_element ] ),

packages/block-editor/src/components/global-styles/use-global-styles-output.js

@@ -703,7 +703,6 @@ export const getNodesWithStyles = ( tree, blockSelectors ) => {
 											.featureSelectors
 									);
 
-								// TODO: Do we need to delay pushing these nodes so they come after the original block's node?
 								nodes.push( {
 									selector: variationBlockSelector,
 									duotoneSelector: variationDuotoneSelector,