Use browser DevTools to check HTTP headers #539
Merged
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
✅ Deploy Preview for i18n-drafts ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
r12a
requested changes
Oct 11, 2023
| </ul> | ||
| <p>Note: W3C has no relationship to any of these services.</p> | ||
| <p>In the HTTP headers, look for the <code class="kw" translate="no">Content-Type</code> header, and in particular for the <code class="kw" translate="no">charset</code> parameter, e.g.</p> | ||
| <blockquote><code>Content-Type: text/html; charset=utf-8</code></blockquote> | ||
| <p>Note: The <code class="kw" translate="no">charset</code> parameter may not be present. This is okay if your document itself indicates its character | ||
| encoding.</p> | ||
| </section> | ||
|
|
||
|
|
||
| <section id="devtools"> |
There was a problem hiding this comment.
We already discussed a better heading.
Btw, these days i use some conventions when formatting source code that help with maintenance. If you'd like to do the same (up to you) i suggest:
- leaving 5-6 empty lines before a section tag (makes it much easier to skip to or find section starts)
- leaving one blank line after a heading
- removing all line indentation, but adding a blank line before each of the following tags: p, ol, li (after the first), etc.
There was a problem hiding this comment.
Thanks for the suggestion. I usually use one blank line after a section tag, and I think that's enough for me.
(Some specs use auto-generated section names in the comment, but I think that's too much.)
r12a
approved these changes
Oct 13, 2023
|
Merging. Copied to CVS as well. |
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.
Fix #491.
I'll update the translations if/when it's approved.