[css-view-transitions-1] Remove resolved issues (#9093)

* Add clarification for writing-mode and other styles.

* Remove resolved issues.

Author: khushalsagar

css-view-transitions-1/Overview.bs

@@ -1684,8 +1684,6 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 			then skip painting |descendant|.
 
 			Note: This is necessary since the descendant will generate its own snapshot which will be displayed and animated independently.
-
-		Issue: Specify what happens with 'mix-blend-mode'.
 	</div>
 
 ## [=Handle transition frame=] ## {#handle-transition-frame-algorithm}
@@ -1702,14 +1700,10 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 				and contains at least one [=animation/associated effect=] whose [=effect target=] is |element|,
 				set |hasActiveAnimations| to true if any of the following conditions is true:
 
-				Issue: The prose around "effect target" is incorrect, but [#8001](https://github.com/w3c/csswg-drafts/issues/8001) needs to land before it can be fixed.
-
 				- |animation|'s [=animation/play state=] is [=play state/paused=] or [=play state/running=].
 
 				- |document|'s [=pending animation event queue=] has any events associated with |animation|.
 
-					Issue: This prose isn't quite right, but it's blocked on [#8004](https://github.com/w3c/csswg-drafts/issues/8004).
-
 		1. If |hasActiveAnimations| is false:
 
 			1. Set |transition|'s [=ViewTransition/phase=] to "`done`".