The new flagging dialog has a vastly reduced clickable area
and, not to put too fine a point on it, that sucks.
In most other similar prompts on the site (e.g. the previous flagging prompt, if I remember correctly, or the vote-to-close prompt) the text below the headers is clickable, i.e. the area in blue:
Not so in this incarnation as ...
Yes it did. I did it.
When the Code of Conduct ships, we're replacing "rude or abusive" with two new categories which you could describe as "rude" and "abusive". As part of that change, we also:
Updated the dialog to use our new "Stacks" design system.
Restructured the language so it's answering a question rather than completing a sentence.
Added a "...
It did change, as already noted.
One request: can we make the font used for the explanations a little bigger? We have room, and this is hard to see (for some people on some devices, at least):
We've got plenty of width, and enough spare height that bumping that up a couple points won't overflow anything. Can we make it bigger?
Or, at least, black? I ...
Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a ...
This was a matter of many people putting in a lot of effort to get some design elements in place while doing a bit of cleanup. We spent more time talking about it and have rolled it back to the previous text with a slight adjustment to the explanation:
It's no longer needed.
The comment is outdated, conversational or not relevant to this post.
As a workaround for until this is implemented (if ever), you can add the rule
to your favorite ad blocker to hide both the indicator beneath the usercard and in the answer field.
This answer previously contained a line of code that would disable this feature for a given site, but that is no longer necessary as SE has changed it to affect all pages rather than just the one.
However, you can install this user script to remove it from all sites, network-wide, permanently, in your browser. As written, this script will permanently ...
I've built a userscript to disable Time Travel mode on all sites, which you can install from here. The updated version (0.3) does not interfere with the fix rolled out by the developers. Thanks to @Makyen, @SonictheWizardWerehog and indirectly to @Bergi for your contributions.
// @name Disable Stack Exchange Time Travel Mode
Yep, our capitalization is all over the place. The tricky part is our localization strings for other communities are based on the original English text. This means that if we change "share" to "Share", our translated communities (Russian, Japanese, Spanish, etc.) each have to re-translate.
We'll be making things more consistent as we refactor and modify ...
I marked this complete since we've resolved it and keep an eye on it when launching new sites, but I think some details are in order because it's not 100% obvious why this happens. Here are some details:
It's a build race condition with the favicon sprite map generation and the cache breaker at the CSS level of PNG copies where the CDN caches an old PNG due ...
Flagging box appears off-center
Free hand circle over the flag that I clicked on with indicated bounds of the center content div.
Screen resolution: 1600x900.
This is so far off-center I feel like I have to turn my head in order to engage with the dialog box. I can understand not wanting it to appear on top of the comment being flagged, but ...
This will be fixed in the next build.
When the accept request completes, it does two things:
Mark all answers as unaccepted (in case we're unaccepting or switching accepted answers).
Mark the newly accepted answer as accepted.
To do that, I have a helper function that switches the ARIA state and sets the appropriate classes:
function setSelected($el, ...
This was apparently triggered by the move to inline "Stacks" validation a few months back. The editor currently supports both inline and old-style pop-up validation messages, but the checks on submission responsible for scrolling (and displaying the message below the button) weren't updated to be aware of the newer styles... As a result, it would fail to ...
How about this:
Why are you flagging this comment?
It's rude or abusive.
It's off-topic or unrelated to this post.
It's outdated, obsolete or not relevant anymore.
In other words, I'd split the middle option into "This is not at all relevant" versus "This used to be relevant but now it isn't."
Instead of Its Not Relevant just have it say: Should be Removed everything else can stay.
This wording gets right to the point: the flagging user believes that the comment is not adding value and should be removed. Nothing more needs to be said, and no reasoning inferred for the flag. If it does then they can use the Something else option.
This is fixed.
The design didn't really consider pages with multiple tags. It was really intended for things like:
Public Questions tagged [asp.net]
You can really tell because your header has [asp.net or vb.net or ...] instead of the correct format, [asp.net] or [vb.net] or ....
I've restructured the header for the tags page so if two or more tags ...
I have been FGITW'd by a cookie edit already, but if for some reason you prefer a userscript solution, let me provide one.
// @name Novikov Self-consistency Enforcer
// @namespace http://tampermonkey.net/
// @version 0.1
// @description Disables time travel on SE (April Fools 2019)
// @author John "Novikov" Dvorak
There are several reasons why certain icons/logos are the way they are.
Copyright: Ask Different is not allowed to use Apple's own logo. They settled for the Mac's Command Key logo instead, which was already 'public domain'.
Size: I personally like the Mathematics logo; when it's in full size you can see it's derived from the Reutersvärd / Penrose triangle. ...
In a manner of speaking - bounties are what you pay for it to get featured. Its an action performed by a user, not a quality of the question.
Bounties feels.. odd in that context. Bountied makes a little more sense, but means nothing unless you get the way we do things already.
The overloading is unfortunate - but you're not going to feature posts outside ...
This is still an issue for our newer users who don't know the site and network's history. For example this question asking what it would take for Bricks to graduate so that we can have a more branded experience:
Criteria for losing "beta" status
This also asks about the Area 51 stats, and my answer explains the questions/day stat.
As the Site Stats ...
Nearly two years ago (when the comment flag dialogue still had five options), Taryn (who was called Bluefeet back then) asked a question on ELU about what a good word would be for a new (replacement) flag option.
A user (well, me, actually) suggested the word “irrelevant” and the answer was accepted. I gave the following as reasoning for why it would be a ...
There is a tour in the StackExchange Network sites, which introduces users to the basics of each community and how to contribute.
Maybe, there should be a user interface tour too.
The location of the StackExchange speech bubble is the upper right corner, which is where usually options are located. This can also be seen in the screenshots from GitHub and ...
Stack Overflow, as the first site on the network, always had sans-serif, I think. It's pretty common for websites. Sans-serif is essentially the default for Stack Exchange sites.
The math site did not start out with serifs. This changed when the site got a design because Jin, the designer at the time, "believe[d] the serif typeface on the header and ...