66191e8a37
For the initial rendering, where there is no transition from a previous visual state to a new one, animations make little sense. The page should load with as few reflows as possible. Similarly, while we typically want to defer updating the SideNav state (e.g. opened/closed) until the "leaving" document is animated out of the page, on the initial rendering (where there is no "leaving" document) this leads to the SideNav flashing (from closed to open). These worked as expected before, but several parts (mostly related to documents with a SideNav) have been accidentally broken in recent commits (e.g. when upgraded to latest material, or enabled animations for DocViewer transitions, etc.). This commit restores the previous behavior by ensuring that (on the initial rendering) the SideNav state is updated as soon as possible and that there will be no animations when: 1. The hamburger button appears. 2. The SideNav is opened. 3. The main section's width is adjusted to make room for the SideNav. PR Close #21695
Safari (7+), iOS (7+) and IE mobile (11) are tested on BrowserStack.
Angular
Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript and other languages.
Quickstart
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.