0 Likes for the x Likes thingie
-
I personally find it hideous and disorienting
-
Haven't we had a flamewar on that already?
-
This is for all the people who didn't read the original flamewar and only now witnessed this hideosity.
-
Like me.
Why isn't it next to the like icon?
-
Doesn't even work right. It says you have one like, but when I push button you have two likes.
-
Also, push button, push like heart. Like section collapses :/
-
And it has a noticable opening delay ...
-
Well that's probably our fault.
Also, nice how hitting "Like" by anyone (still?) closes the unrolled like pane and makes the page jerk upward. As in, do exactly what the update was attempting to prevent. ( 'd)
-
Also, nice how hitting "Like" by anyone (still?) closes the unrolled like pane and makes the page jerk upward. As in, do exactly what the update was attempting to prevent. ( 'd)
Well done,
-
-
And it's still ugly and lacking contrast, and it's hard to tell by skimming the thread which posts are potentially interesting. Good job, good job, I'm thriving with anticipation for the next UI upgrade..
-
and it's hard to tell by skimming the thread which posts are potentially interesting
This. This is the worst thing about this change.
Although, you can CSS the thingie purple or whatever, so that's at least ... something?
-
Why isn't it next to the like icon?
Because I was being lazy when I pre-empted its arrival - I'll move it in a sec...
-
Although, you can CSS the thingie purple or whatever, so that's at least ... something?
Or make it a heat mapped value (that might be a bit difficult with only CSS, though ... don't really know).
-
-
-
I'd have it to the right of the likes button, but that's just me...
-
Also, push button, push like heart. Like section collapses :/
A bug was filed about that before we even got it. They are "working on it."
-
And it has a noticable opening delay ...
Of course, it has to request the data from the server, and the server probably sends a list of all the likes in the current thread and lets the client filter down to the relevant information. Just like the server sends a list of all the post numbers every time you get a new batch of posts in a topic.
-
And it's still ugly and lacking contrast, and it's hard to tell by skimming the thread which posts are potentially interesting. Good job, good job, I'm thriving with anticipation for the next UI upgrade..
They said something about "making smaller posts more readable." I asked what they meant, but they refused to respond to my query.
-
Or make it a heat mapped value (that might be a bit difficult with only CSS, though ... don't really know).
NO!
-
Of course, it has to request the data from the server, and the server probably sends a list of all the likes in the current thread and lets the client filter down to the relevant information. Just like the server sends a list of all the post numbers every time you get a new batch of posts in a topic.
Oddly enough, no.
GET https://what.thedailywtf.com/post_actions/users?id=485608&post_action_type_id=2&_=1437405653275 200 [{"id":922,"username":"aliceif","uploaded_avatar_id":23060,"avatar_template":"/user_avatar/what.thedailywtf.com/aliceif/{size}/23060_1.png","post_url":null}, {"id":18,"username":"boomzilla","uploaded_avatar_id":13465,"avatar_template":"/user_avatar/what.thedailywtf.com/boomzilla/{size}/13465_1.png","post_url":null}, {"id":83,"username":"locallunatic","uploaded_avatar_id":19795,"avatar_template":"/user_avatar/what.thedailywtf.com/locallunatic/{size}/19795_1.png","post_url":null}]
As to why the endpoint is named
users
, and whypost_url
is null...
-
@abarker said:
Of course, it has to request the data from the server, and the server probably sends a list of all the likes in the current thread and lets the client filter down to the relevant information. Just like the server sends a list of all the post numbers every time you get a new batch of posts in a topic.
Oddly enough, no.
GET https://what.thedailywtf.com/post_actions/users?id=485608&post_action_type_id=2&_=1437405653275 200 [{"id":922,"username":"aliceif","uploaded_avatar_id":23060,"avatar_template":"/user_avatar/what.thedailywtf.com/aliceif/{size}/23060_1.png","post_url":null}, {"id":18,"username":"boomzilla","uploaded_avatar_id":13465,"avatar_template":"/user_avatar/what.thedailywtf.com/boomzilla/{size}/13465_1.png","post_url":null}, {"id":83,"username":"locallunatic","uploaded_avatar_id":19795,"avatar_template":"/user_avatar/what.thedailywtf.com/locallunatic/{size}/19795_1.png","post_url":null}]
As to why the endpoint is named
users
, and whypost_url
is null...It was a joke. I wasn't … I wasn't being serious.
And I just realized that my composer CSS isn't being applied. That means that they changed the class name for the composer.
-
I think it's OK.
It does reduce the visibility of likes a bit too much, but just making it black instead of light gray would be enough IMO (could we try that with our super custom CSS?). Maybe it was intentional, I can't be arsed to read the jeffguments for it.
-
And it's still ugly and lacking contrast, and it's hard to tell by skimming the thread which posts are potentially interesting.
Look for the icon of Godzilla fighting a giant rat.
-
And you'll know which to skip.
-
-
Is it just me?
-
You're on mobile; that's different.
-
Is it just me?
Well, I got beat to the joke, so I'll actually try to be helpful:
No, it isn't just you. The latest beta has issues updating client session that were started before we updated to the current beta. You need to do a hard refresh, though there has been some success with soft refreshes.
Good luck.
-
That means that they changed the class name for the composer.
It's now a class and not an ID, which kills the nasty bug where visiting your preferences would break the composer, causing any further edits to not save.
-
@abarker said:
That means that they changed the class name for the composer.
It's now a class and not an ID, which kills the nasty bug where visiting your preferences would break the composer, causing any further edits to not save.
Yeah, tracked that down:
https://what.thedailywtf.com/t/local-dischorse-css/47600/159?u=abarker
-
Thanks!
-
bikeshedding allday errday
-
why post_url is null..
Well, if it's
post_actions
, presumably that includes flags?
-
@pjh this really needs to be done here:
its really odd having
</>
after likes, forces you to push a button about each time you like something.
-
Look for the icon of Godzilla fighting a giant rat.
Is that what that is? I'd never bothered to blow it up, so it just looks like some kind of mould.
-
-