ScrollService instances after each test (#33937)
		
			
			`ScrollService` subscribes to global `window` events and mutates global state in the listener (e.g. read/write values from/to `sessionStorage`). Therefore, we need to always call its `ngOnDestroy()` method to unsubscribe from these events after each test. In f69c6e204, a new testcase was introduced that was not destroyed. As a result, random failures started to randomly happen in other, unrelated tests ([example CI failure][1]). This commit fixes this by ensuring all `ScrollService` instances are destroyed after each tests (provided that they are created with the `createScrollService()` helper). [1]: https://circleci.com/gh/angular/angular/533298 PR Close #33937
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.
					Languages
				
				
								
								
									TypeScript
								
								68.6%
							
						
							
								
								
									HTML
								
								12.8%
							
						
							
								
								
									JavaScript
								
								8.4%
							
						
							
								
								
									Pug
								
								7%
							
						
							
								
								
									Starlark
								
								1.4%
							
						
							
								
								
									Other
								
								1.7%