That's status-bydesign. This is how that widget looks for the owner (except that this is a different badge):
Until they've made a choice for which badge to track next, they will be registered as tracking that particular badge. And this is how their profile will look to others:
That's intentional. Check this link which sports the same message as you saw:
What happens here is that I list all questions with the tags tag ... with a bounty on them. Currently, there are none, but if you select a different tab, e.g. 'Newest' or 'Active', you do see questions.
Of course, if there are no questions at all in the tag anymore, select a ...
As has been mentioned in the comments, we've had a fair number of issues with our search cluster over the past few weeks - from DDOS to hardware issues. It's certainly in a more stable state than it was after that bunch of fun, but it's still a little delicate and, as you saw this morning, it had a bit of a blip. Of the ~16.5k search requests within a 20 ...
I personally consider this status-bydesign.
When new chat messages are sent, the chat script will naturally scroll downward to accommodate the new message. With this dropdown open, if more messages are sent, it would feel a bit weird if the dropdown started moving upwards with the rest of the messages. If you've got that dropdown open and are about to click &...
This bug is now status-completed as a result of the migration to CommonMark.
Basically, the prior renderer had an ambiguity in its specification. Essentially, block quote markup on separate lines would be combined into a single block quote when rendered, but spoilers were not to be combined. So the following markup:
I can confirm that it is indeed the thickness of the line that makes the (donut)hole disappear.
If you access the image of the four directly from the server you can tweak its HTML code.
Originally the "stroke-width" is set to 7, changing it to 3 results in the following image:
For me the focus isn't on the entire image itself:
It is on the "enter image description here" part only.
So continuing to type after the image upload results in typing an image description, which is a very much likeable result, as images do need more image descriptions.
This also occurs when on the ask page, and entering a title.
I am using ...
It used to be a link, until spammers abused it one time too much. As a link, it was useful since it could be clicked no matter what part was visible.
Now that it's plain text, when it's cut it's useless.
My suggestion is to move that field into the About Me box, as it's just extra info about the user.
Mockup using my own data: (fake details)
This way there ...
The solution is to allow cookies for Stack Overflow. Sometimes browsers tend to automatically block cookies but if you allow them you're good to go.
Steps to allow third party cookies in Chrome browser:
Click the More icon (), then click Settings.
Click "Privacy and security" in the left navigation bar.
Click "Site Settings".
As can been seen in the linked question revisions, the "status-completed" tag was added by animuson in Revision #7 on Oct. 8, 2015 at 20:58. Within that same minute time period, Animuson also posted a comment stating
This is now possible as part of the close vote aging system, though you have to wait at least 14 days after you retract your vote to ...
I believe the feature was marked as completed because close votes expire after 14 days, allowing the caster to re-cast.
We can't recast a retracted close vote right away, but I'm pretty sure that the retracted close vote ages away and expires like actual close vote, after 14 days, allowing us to re-cast it. (Assuming the question wasn't closed in the ...
So, this question led me through a wild goose chase down the code, to figure out why this would be happening. Since the Community User does have a metadata record, with exactly one pageview recorded. And the logic is in place to record it when the profile pages are loaded.
The process for saving new profile views is actually pretty optimized. It is async ...
One of the nodes in our primary Elastic cluster has been having a few issues (we suspect a hardware issue at this point) that have resulted in it randomly re-allocating shards across nodes. For, as yet, unknown reasons it drastically degrades cluster performance resulting in timeouts and intermittently taking the entire cluster offline. We're in the process ...
Sorting is now removed from these tables in the new mod ux for review suspensions, due to the exact points that you made.
There is now filtering available on that page which allows for searching by User ID or profile URL.
useless table sort
removed in new interface
try filter instead
The drop down on the top right can only be seen by you, so hidden communities have nothing to do with it. Hidden communities affect what is shown on your profile page.
You can click on “edit” next to ”my communities” to change what you see in the upper right drop down. By default I think it will show the top 4-5 communities where you have the most reputation....
That's not what "hiding" does. Hiding a community means that it's not visible to other users but it still remains visible to you.
If you want to remove a site from your site switcher favorite communities, click the (easily-missed) "edit" button and remove it manually.