Added a question about <link> and <script> positioning #245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For the "exceptions" part, this is extracted from Google Analytics official guide:Paste your [GA script] (unaltered, in its entirety) into every web page you want to track. Paste it immediately before the closing </head> tag. Nah. We had various discussions about it in html5 boilerplate: h5bp/html5-boilerplate#1614. A better example would be Modernizr, which has its reasons to be in our |
|
Nice discussion you guys have there. Does that render my proposed question invalid though? |
|
No, for sure not. Was just saying :) |
| @@ -57,6 +57,8 @@ This file contains a number of front-end interview questions that can be used wh | |||
| * Consider HTML5 as an open web platform. What are the building blocks of HTML5? | |||
| * Describe the difference between cookies, sessionStorage and localStorage. | |||
| * Describe the difference between `<script>`, `<script async>` & `<script defer>`. | |||
| * Why is it generally a good idea to position CSS `<link>`s between `<head></head>` and JS `<script>`s just before `</body>`? | |||
| * Do you know any exceptions for this rule? | |||
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
|
👍 |
darcyclarke
added a commit
that referenced
this pull request
Jan 30, 2015
Added a question about <link> and <script> positioning
MUDev1994
pushed a commit
to MUDev1994/Front-end-Developer-Interview-Questions
that referenced
this pull request
May 26, 2023
Added a question about <link> and <script> positioning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Yet another question I find myself asking candidates more than often. These are rather old practices (Yahoo!'s Best Practices for Speeding Up Your Web Site article is turning nine this year) but, to my knowledge, still apply.
For the "exceptions" part, this is extracted from Google Analytics official guide:
I guess this exception applies to all tracking scripts.
Side: The question can lead to discussions about sync/async script loading.