Hot answers tagged

9

The second question was migrated from Super User. I think this confuses the code that decides which of asked/answered/modified to display on the home page. It either needs to say "migrated" or find out the most recent of the "normal" changes and display that.


7

Comments don't support HTML, merely a small subset of Markdown. See: https://webapps.meta.stackexchange.com/editing-help#comment-formatting (you'll find this by clicking the "help" link under the big Add Comment button).


6

This is by design and is a recent change. The syntax you see inserts the image and creates a link to the image. This way images that are larger than the column for posts can be scaled down in the post but the full version of the image is easily gotten to. The syntax to do that has been around for a long time, it's just that the image button was recently ...


6

I suspect that you have click "featured" from the homepage then navigated to tagged/facebook. It will keep your initial selection when browsing elsewhere e.g. through each of the tags.


6

A while back there was some issue with the wildcard expansion generating excessively long URLs that would be rejected by the web server. Jeff imposed an expansion limit as a workaround, which seems to limit the wildcard matches to the top 20 most popular applicable tags.


4

This will be fixed in the next build; for details see my answer on Meta Stack Exchange.


4

There are a handful of redundant phrases - including some containing the name of the tag itself - that are not displayed on tags list, to help ensure there's room for the non-redundant parts of the tag excerpt. The google spreadsheets tag wiki doesn't match any of these, so it's displayed in full. For details, see: New tags page mangles tag wiki excerpts


4

This should be resolved now with the correct spacing (unless an employee corrects me)


4

The decision whether this error is rendered is made on the server when the add comment link is rendered (it has an additional data-reg="true" attribute), since it also depends on other things that would require an additional round-trip to the server each time a user clicks this button - which we don't want. After you've reached the required rep you need to ...


4

This appeared in the review queue for late answers and the user was classed as new as they only had one previous answer (which was deleted)


3

Geoff Dalgas♦ says this issue has been fixed: You have caught my attention on this one. A fix has been pushed and will build out soon. I also want you to know that our design team has been hard at work at converting all of our .less files to a consistent and uniform layout which will solve most of these issues in the future. Thanks for the report and we'...


3

I had a look earlier when there were 4 questions & now, which has 5 featured questions, and both cases the number's shown correctly. It's probably a caching issue.


3

From the Meta post What does "You don't have the permission to use this type of flag" mean? Figured it out. It happened only when the user hit the flags tab via the /tools route, since it was the last /tools tab he had open. Fixed in next build that rolls out (before that happens you can simply work around by clicking visiting /tools/flagged). ...


3

In the rare cases where this happens, it's supposed to - we don't want them making the page extremely long when added up.


3

There are always some number of rendering inconsistencies between the mobile and desktop versions of Chrome, even if you're not using any beta versions. That's why we have a mobile version of the site, accessible via the "mobile" link in the footer - I can confirm that the table (while indeed poorly-rendered in the full site on mobile Chrome) appears ...


3

Geoff Dalgas♦ says this issue has been fixed: You have caught my attention on this one. A fix has been pushed and will build out soon. I also want you to know that our design team has been hard at work at converting all of our .less files to a consistent and uniform layout which will solve most of these issues in the future. Thanks for the report and we'...


3

This is what happens when we merge questions, specifically In GMail, is it possible to reverse "always display images from" decisions? from 2010.


3

The next build will have a fix for this styling. Thanks for the report.


3

The fix is on dev server now, will be deployed to live in our next production build.


3

Usually, that generic error indicates something transient and/or something on your end that's the problem. Try again later Try again with a different browser Try again on a different network (if possible) Try again with browser extensions/add-on off


3

Good call. We (well, Josh mostly) recently did a lot of work to consolidate the bajillion LESS files used for all the Stack Exchange sites. Before that, this bottom border didn't exist on webapps.se, so it was configured to be white, i.e. invisible. This actually looks wrong in some places as you found, but even where it doesn't, the current "you are here" ...


2

The number appears to be your total StackExchange network reputation rather than your WebApps reputation. Meanwhile, badges are only shown from accounts with more than 200 points. This is similar to the rules for Flair, except since you need a minimum of 20 points to chat I guess it counts them all. See also this meta SO discussion.


2

The inbox message relates to this question which was closed as a duplicate of this question. You asked the initial question (and is actually where the comment is) hence why you get the notification. I guess SE have implemented some redirection based on the whether the question is closed or not. As this is a duplicate it automagically redirects you to the ...


2

I cannot reproduce this, but I'm going to assume it was there initially and someone from SE Team fixed it. Marking this as resolved.


2

The fix will be in the next production build, sometime after midnight tonight EST or tomorrow.


2

The margin is definitely off. I put in a fix for this, will be on live after our next prod build(within 24hrs). Thanks.


2

I can't reproduce this, which makes me think it's a local font issue like John C mentioned. Not much I can do about that.


2

What seems to have happened is that the suggested edit was looked at - the reviewer decided to improve it but also unselected the checkbox for "this edit was helpful", causing the suggested edit to be rejected, but also for your changes to be incorporated into his edit.


2

As balpha mentions on Meta, the [tag:] syntax is intentionally designed to link to a specific tag, making this status-bydesign.


Only top voted, non community-wiki answers of a minimum length are eligible