Hot answers tagged

5

The reason is that the .post-text class, to which the "real" post belongs, has a :visited pseudo-class for links which alters their colour. When you are editing, the edited text appears in a div of class wmd-preview, which does not alter the colour of visited links. It may be that this feature is by design. It may be that the wmd-preview class should alter ...


4

41. This is how you can make the 41 show properly. 41\. This is how I did it, by escaping the period following the number with a backslash. Using code markup to offset something that isn't code isn't a great idea for searchability and other reasons. Instead, in situations such as this, just properly escape whatever you need to and it will appear as ...


3

No, it's not supposed to be this hideous. There were some left-over styles still being applied from back in the days when that page was hideous-by-design (as in the question from May that you're referring to). Since that page's layout has been updated to match the rest of the site, that's no longer necessary. It'll look as expected after the next build of ...


3

This will be fixed in the next build (after rev 2012.5.9.2511).


2

Yes, the colors for the HNQ have changed. But visited and unvisited links are different colors for me on main, so I need to ask: Have you clicked any of those links? I checked the Wayback Machine for August 16 on the main site and it shows this: This isn't a particular surprise, since it was announced ages ago that there would be changes to themes (among ...


2

I am unaware of a recent change. My browser presents two colors for links in that sidebox. Visited links are #555. Unvisited links are #333. They are hard to differentiate visually. Here is the relevant CSS: .question-hyperlink, .answer-hyperlink { color: #333; line-height: 1.3; margin-bottom: 1.2em; } .question-hyperlink:visited, .answer-...


2

Take it away! Thankfully I do not see it yet, but it looks awfully distracting. Or at least make it optional. Actually, many more things should be made option, like adding a break line that shows where comments are "abridged", etc.


2

I agree that the ugly and freakily colored monospace that you get from backquotes makes next to no sense and is a real pain. In fact, I talk about that in this question. But one real exception is that we have no other ways of doing tables for a code block. And yes, there really are times that you want exact column placement. (S (NP (NP The dial) (...


2

This will be fixed in the next build (after rev 2012.5.9.2511).


1

Thanks for reporting this. I have already made some changes that should have made this a non-issue, and have added some more to ensure consistent look and feel. This feature is currently being A/B tested, so you may not be able to see it again for a while...


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