Question 9. Throttling is weird. Create async store with requests map. If requests is not yet resolved (so present in the map) the code prevents another invocation + button is disabled
Answer to the first question is incorrect. CSS is downloaded and parsed in parallel to the DOM creation, but the actual rendering (i.e., displaying the styled content on the screen) can't occur until both the DOM and CSSOM are fully constructed.CSS is downloaded and parsed in parallel to the DOM creation, but the actual rendering (i.e., displaying the styled content on the screen) can't occur until both the DOM and CSSOM are fully constructed.
Hey Santosh, good addition. To clarify: CSS and the CSS DOM must be fully dowloaded, parsed and interpreted before rendering starts. The DOM creation is incremental, which means we can build the DOM as we go, and start rendering before the DOM is finished - which is not the case with CSS. All CSS in the tag must be downloaded and parsed before we can start rendering. As the MDN docs put it: " While the DOM construction is incremental, CSSOM is not. CSS is render blocking: the browser blocks page rendering until it receives and processes all the CSS. CSS is render blocking because rules can be overwritten, so the content can't be rendered until the CSSOM is complete."
@therealseniordev Yes, what you said makes sense,so the answer would be "after" right? Render happens after the DOM is created. Once both the DOM and CSSOM are complete, the browser combines them to create the Render Tree.
@therealseniordev As the browser starts downloading and parsing the HTML, it incrementally constructs the DOM tree. When the browser encounters a or tag in the HTML, it fetches and parses the CSS in parallel while continuing to parse the HTML. So, CSS rendering happens parallel with DOM creation/after. Please correct me if I am wrong.
Yes, the browser does build the CSS and the DOM in parallel, but it wont render until the CSSOM is finished. So CSS is blocking in the sense that it stops the rendering -> it does not stop the DOM building which can run concurrently.
🚀Find Your Technical Gaps With This FREE 10-Minute Technical Assessment
learn.theseniordev.com/technical-assessment
Nice collection of questions and pretty well explained. Keep it going. Thanks !
Thanks for posting these questions. Appreciate it. Would love more of these kind of videos.
Sure Srinu, we are working on more of them, and you will see some of them soon
Great video! Small issue, but I think you mentioned the microtask queue a few times when you meant to say the task queue
Question 9. Throttling is weird. Create async store with requests map. If requests is not yet resolved (so present in the map) the code prevents another invocation + button is disabled
Great
pls do a video about angular js interview questions.
Is a bit out of scope for us at the moment but we might consider it in the future
Answer to the first question is incorrect. CSS is downloaded and parsed in parallel to the DOM creation, but the actual rendering (i.e., displaying the styled content on the screen) can't occur until both the DOM and CSSOM are fully constructed.CSS is downloaded and parsed in parallel to the DOM creation, but the actual rendering (i.e., displaying the styled content on the screen) can't occur until both the DOM and CSSOM are fully constructed.
Hey Santosh, good addition. To clarify: CSS and the CSS DOM must be fully dowloaded, parsed and interpreted before rendering starts. The DOM creation is incremental, which means we can build the DOM as we go, and start rendering before the DOM is finished - which is not the case with CSS. All CSS in the tag must be downloaded and parsed before we can start rendering. As the MDN docs put it: " While the DOM construction is incremental, CSSOM is not. CSS is render blocking: the browser blocks page rendering until it receives and processes all the CSS. CSS is render blocking because rules can be overwritten, so the content can't be rendered until the CSSOM is complete."
@therealseniordev Yes, what you said makes sense,so the answer would be "after" right? Render happens after the DOM is created. Once both the DOM and CSSOM are complete, the browser combines them to create the Render Tree.
@therealseniordev As the browser starts downloading and parsing the HTML, it incrementally constructs the DOM tree. When the browser encounters a or tag in the HTML, it fetches and parses the CSS in parallel while continuing to parse the HTML. So, CSS rendering happens parallel with DOM creation/after. Please correct me if I am wrong.
Yes, the browser does build the CSS and the DOM in parallel, but it wont render until the CSSOM is finished. So CSS is blocking in the sense that it stops the rendering -> it does not stop the DOM building which can run concurrently.
❤❤❤❤❤❤❤❤❤
Glad you enjoyed it :)