Paging PJH
-
The style that fixes the bullshit 'way off on the right side whitespace hyperlink because we're assholes' is gone.
Please remove the clickable links that expand past the text on reply/respond as new topic that float off to the side of the page!
-
The style that fixes the bullshit 'way off on the right side whitespace hyperlink because we're assholes' is gone.
I don't see that.
-
-
I see this:
-
Are you talking about this? (The "Widescreen+minimal' style.)
-
TDWTF default::
Discourse Default:
Widescreen+min:
I've changed nothing. I suggest you change CSS styles.
-
can't reproduce on any of my browsers.... what browser and version are you using?
-
can't reproduce on any of my browsers.... what browser and version are you using?
Reproducible under FF34.0.5 with Discourse Default - I can only assume that's what he's using.
-
hmm... i should install FF again.... if for no other reason than it seems to bring out the discourse bugs.
-
Chrome latest
-
-
Chrome Version 39.0.2171.95 (64-bit):
No repro I'm afraid...
-
I assume he's talking about when you hover over any of those items. All 3 highlight for me.
I get the same as @Matches using Chrome Version 40.0.2214.111 (64-bit) on Linux.
-
I assume he's talking about when you hover over any of those items. All 3 highlight for me.
they do, because they are the same item really. the javascript that adds them doesn't split them into different items (maybe it can't)
-
I "know." I assume @Matches doesn't, though, since he probably doesn't read every damn thing on here all the time, though, like some people.
-
I was pointing out that my * is on TDWTF style which @PJH claims is fine.
-
I assume he's talking about when you hover over any of those items. All 3 highlight for me.
No - it's the excess href target in the space to the right of the "Reply as linked Topic" seen here in Discourse Default:
But for me on Chrome (and Firefox), TDWTF Default doesn't have it, stopping - as it does - at the end of the anchor text:
@Matches' problem seems to be he's seeing the former on the latter, which I can't reproduce.
What is strange, however, is that he appears to have TDWTF Default selected (in the second screenshot), but (in his first screenshot) he doesn't have the </> button either.. which indicates that for some reason he's on Discourse Default.
@Matches - can you check your cookies for a what.thedailywtf.com cookie called
preview_style
, delete it and hard-refresh.
-
... that's what the star means?
I feel like a complete idiot now.
-
... that's what the star means?
I feel like a complete idiot now.
I'm also an idiot, for the same reason.
-
-
I stuck it there so I'd know whether or not the CSS were actually taking and which I was using/testing at any particular point in time...
-
I stuck it there so I'd know whether or not the CSS were actually taking and which I was using/testing at any particular point in time...
I wish I'd known that. I spent 17 hours looking for the associated footnote.
-
In related news, programming texts are a missing footnote nightmare.
-
it seems to bring out the discourse bugs.
There aren't enough of those already? You actually want more?
-
There aren't enough of those already? You actually want more?
no, and yes. in that order.
-
-
@accalia Is Doing It Wrong™
-
edits don't count!
-
How about this?
<!LikeBot ! wrong>
-
..... sure that counts but i was shouting about @codinghorror bot doing what he's about to only the first time @loopback0 had to edit his post to make it work .
-
I think @LikeBot is dead D:
-
hmm.... what about @zoidberg?
-
Tired of Discourse? Why not @Zoidberg?
-
he's alive!
-
Factoid error: No such factoid exists.
-
You requested
wrong>
. And>
is a valid factoid name, because I'm doing it wrong.
-
<!LikeBot ! wrong
-
@> is Doing It Wrong™
-
Factoid error: No such factoid exists.
-
!LikeBot factoidinfo wrong
-
Factoid 'wrong'
Created on 2015-TO-DO by @TODO
Source:@%iorr% is Doing It Wrong™
-
-
touche.
-
@loopback0 said:
There aren't enough of those already? You actually want more?
no, and yes. in that order.
And people think I'm crazy…
They're right, but still…
touche.
I think your acute accent fell off and collapsed into a full stop
-
en-US keyboard layout. typing accents is a pain in the tail.
-
I thought you had that WinCompose thing? Or something like it. So you'd just type Alt Gr'e. And I'm pretty sure ' is in the same place on en-US and en-GB layouts.
-
i have a couple of custom ones mapped (in particular interobang) bt not on all my computers because.... well i guess i'm just discoursistent. :-P
-
If you have Alt Gr, surely you just press Alt Gr + e
-
Alt Gr + e
WinCompose stops that working for me (it hooks into that key so I can type ☺ and ‽ and ö and ♯ and stuff), but Ctrl+Alt+e does still work.
-
Alt Gr + e gives me €