Skip to main content
FTP links are allowed, per the linked post - I just tested it
Source Link
  1. href=""
    This attribute can only hold proper URL links, such as https://stackexchange.com/users/, or relative or protocol-relative URL links such as /q/3122 or //stackexchange.com/users/. They cannot hold other types of links, such as relative fragments (e.g. #3122), or protocols other than HTTP or HTTPSprotocols other than HTTP, HTTPS, or FTP (e.g. javascript, ftp, or mailto, or magnet). Invalid hrefs will strip the entire <a> tag.*
  2. title=""
  1. href=""
    This attribute can only hold proper URL links, such as https://stackexchange.com/users/, or relative or protocol-relative URL links such as /q/3122 or //stackexchange.com/users/. They cannot hold other types of links, such as relative fragments (e.g. #3122), or protocols other than HTTP or HTTPS (e.g. javascript, ftp, or mailto). Invalid hrefs will strip the entire <a> tag.*
  2. title=""
  1. href=""
    This attribute can only hold proper URL links, such as https://stackexchange.com/users/, or relative or protocol-relative URL links such as /q/3122 or //stackexchange.com/users/. They cannot hold other types of links, such as relative fragments (e.g. #3122), or protocols other than HTTP, HTTPS, or FTP (e.g. javascript, mailto, or magnet). Invalid hrefs will strip the entire <a> tag.*
  2. title=""
This used to be true fully in the past, but after the switchover to CommonMark, it has changed somewhat.
Source Link

Any tags not in the above list will be stripped out of the post. Do note that the sanitizer that strips out tags willmay falsely recognize any text between < and > characters as HTML, and so anywhich may cause such text willto be stripped out of the post; to prevent this, encode those characters as &lt; and &gt;.

Any tags not in the above list will be stripped out of the post. Do note that the sanitizer that strips out tags will recognize any text between < and > characters as HTML, and so any such text will be stripped out of the post; to prevent this, encode those characters as &lt; and &gt;.

Any tags not in the above list will be stripped out of the post. Do note that the sanitizer that strips out tags may falsely recognize text between < and > characters as HTML, which may cause such text to be stripped out of the post; to prevent this, encode those characters as &lt; and &gt;.

minor clarification why you need to scroll
Source Link
wjandrea
  • 660
  • 3
  • 14

Note: This table overflows to the right. Press your middle mouse button and wave your mouse left or right to scroll the tableit, or use your laptop's trackpad (if applicable):

Press your middle mouse button and wave your mouse left or right to scroll the table, or use your laptop's trackpad (if applicable):

Note: This table overflows to the right. Press your middle mouse button and wave your mouse left or right to scroll it, or use your laptop's trackpad (if applicable):

Notice removed Comments only by TinkeringbellMod
Post Unlocked by TinkeringbellMod
Combine <dl> with sub-tags, since they should be used together. Clarify what <li> applies to. Can now use parens for <ol>. Simplify <ul> Markdown and make the HTML match.
Source Link
wjandrea
  • 660
  • 3
  • 14
Loading
People will understand the thml tag <b> a little better if the word "bold" is used in the description of the <b> tag.
Source Link
Loading
Mobile theme no longer exists
Source Link
Loading
Using some fancy dynamic third party image generator might have been funny in the past but 1) huge security risk, and 2) image rot. Really bad idea, much better to use static and safe image.
Source Link
Shadow Wizard
  • 174.9k
  • 33
  • 437
  • 863
Loading
deleted 4 characters in body
Source Link
Loading
added 610 characters in body; added 70 characters in body; added 93 characters in body
Source Link
Loading
added 73 characters in body
Source Link
Loading
deleted 4 characters in body
Source Link
Loading
Non-discriminating language
Source Link
Loading
Reason for rollback was Unicode characters; other changes were fine, per https://chat.stackexchange.com/transcript/message/59582393#59582393
Source Link
Loading
Rollback to Revision 28
Source Link
Makyen
  • 25.5k
  • 8
  • 48
  • 84
Loading
Unicode magic
Source Link
Loading
added 850 characters in body
Source Link
Loading
Rollback to Revision 25
Source Link
Emil Jeřábek
  • 1.6k
  • 2
  • 12
  • 16
Loading
Rollback to Revision 24 - That's not actually true. They are officially supported, such as in <!-- language-all: [...] --> comments. What that post says is that <!-- [...] > gets misrecognized as an invalid HTML element, and so gets stripped.
Source Link
Loading
As per the answers to https://meta.stackexchange.com/q/120415, HTML comments are NOT among the allowed HTML tags. They only appear to work by accident, as they are removed just like any other unrecognized tags.
Source Link
Emil Jeřábek
  • 1.6k
  • 2
  • 12
  • 16
Loading
Stack Exchange (with a space) is the name.
Source Link
Makyen
  • 25.5k
  • 8
  • 48
  • 84
Loading
Add H4–6
Source Link
Makyen
  • 25.5k
  • 8
  • 48
  • 84
Loading
edited body
Source Link
Glorfindel Mod
  • 255.6k
  • 61
  • 638
  • 1.3k
Loading
added 744 characters in body
Source Link
user805262
user805262
Loading