This has been "fixed". We still do not support the groovy language explicitly, but syntax autohighlighting should at least kick in for unrecognized lang-* language overrides (on sites that allow for it, such as Stack Overflow). Due to not officially supporting the groovy syntax, this may have unintended highlighting depending on what language ...
I have no idea. It's been like that since the initial version in 2013, which may have been copied from somewhere else when the new help center was being filled. So who knows how old that text actually is or what reference it was trying to make regarding flags.
I removed the reference to flagging in the line because it clearly does not make sense today.
Any chance this will lead to improved (safe) HTML support in the future?
Rendered versions below — all failing at time of posting
From The Suicide of Socrates: On a day in 399 BC the philosopher Socrates stood before a jury of 500 of his fellow Athenians accused of "refusing to recognize the gods recognized by the state" and of "corrupting the youth."...Socrates was 70 years old and familiar to most Athenians. His anti-democratic views had turned many in the city ...
Firstly, the difference between 1.3 and 1.6 for the new line-height changes is actually 1.45, not 1.5. Second, I would like to have the line-heights added as options in preferences, which would be a real accessibility improvement.
Upon writing the related Answer below, I needed to copy the badge descriptions for Publicist, Booster, and Announcer.
https://meta.stackexchange.com/a/354077/281934 see what I did there?
Publicist: Share a link to a post later visited by 1000 unique IP addresses. This badge can be awarded multiple times.
It appears that the Share Link badges were quietly ...
Given that the design system documentation explicitly mentions small text, is there a chance of finally getting the <small> tag as allowed HTML in Markdown posts? The case for <small> has been made many times and, most saliently, people liberally abuse <sup>/<sub>/both as a workaround, so all the arguments against introducing the tag ...
Links around code don't show up on the mobile site
See the screenshot of an answer of mine (as it appears on both Firefox and Chrome on Android):
Note that I refer to "documentation I have linked" yet don't appear to have linked anything.
In reality I've actually inserted a link around the function name as follows
... use [`PyArray_ZEROS`](http://...
The text has been changed to:
… Always quote the most relevant part of an important link, in case the external resource is unreachable or goes permanently offline.
I agree, this is the intent, and see how it can be confusing.
site is up, link down
quote relevant content please
and all will be good
Single-line lists (without <p>) have a large amount of spacing:
This looks exactly the same as lists with paragraphs:
Lists without blank lines between the items shouldn't get rendered as a paragraph (and they don't, no <p> tag), and ...
I want to draw readers' attention, particularly that of @AaronShekey, to the fact that the W3C does not actually recommend setting the line height to 1.5 or higher.
The relevant recommendations seem to be WCAG criteria 1.4.12 (Text Spacing) and 1.4.8 (Visual Presentation).
Criterion 1.4.12 regarding text spacing reads:
In content implemented using markup ...
This is taken care of. If you are on the review stats page for a queue where you cant review, you will not be shown the link to review.
check out those cool stats!
link to review no longer taunts
for low rep user
Elastic's rebuilding of related questions was causing some issues a little while back and we did some work to stabilize our internal cluster. Fixes have since been deployed but the mechanism and how it inter-relates to new questions changed as well. In short: we had this turned off for old question rebuilds and inadvertently affected new question rebuilds.
This is my fault, a side-effect of some infrastucture changes. Sorry. Working on getting a fix out ASAP.
For those who are interested in code things: some newly "async" code was not properly "awaited", and the result (now a future/promise, not a value) was handed to a JSON serializer, which duly serialized... the future/promise :(
I fail to see why a refactoring of the post styling code is applied along with significant changes to that formatting. In my experience it is common wisdom that you refactor your infrastructure first without changing user-facing behavior (as much as this is possible of course), then make behavior changes while resting stably on the new infrastructure.
I am ...
By adding support for more heading sizes, h1 looks too big now and breaks some older posts:
The old h1 size (or # in MD) was closer to the current h2 font size, and the author of the post screenshotted above likely intended it as an h2 heading due to its size. The increase in size changes the intended ...
This was very likely a race condition completely at my own fault. I triggered an account merge almost immediately after issuing the network suspension, which caused the account's Id number to change and for the code to fail to network-suspend the remainder of the profiles. I should have waited until all the profiles were suspended before doing that.
There's no way to reveal the spoiler on a user profile.
Also, when I hover the mouse on the spoiler's Markdown content while editing the profile, the "Reveal Spoiler" option disappears.
This is what I have while editing the profile:
And this is when I hover the mouse on the Markdown content:
Let's do what we do best as programmers ;)
⭐Revert Stack Exchange Formatting⭐
Google Chrome Extension (customizable)
Greasemonkey / Tampermonkey script | (only line-height)
Stylish theme (+ Stylus)
PLEASE UPDATE SCRIPTS: fixed a bug where the first line in code blocks had small left indent + added old compact paragraph spacing (Sep 1, 2020)