<IMG> height attribute doesn't work...
-
Still broked
-
There we are, no preceding text works!
-
Nope; rebake fucks it over
-
Or it did …
-
Just like @RaceProUK earlier, I saw it flash to the correct result, then it went back to wrong. Trippy.
-
Well, it worked on try, until I refreshed the page.
-
Just like @RaceProUK earlier, I saw it flash to the correct result, then it went back to wrong. Trippy.
Wait, does this mean they are dishing out the client baked version while waiting for the server baking to be done?
Cause that's fracking retarded.
-
Yes that's what it does. It inlines the client (preview) baked while 'saving' shows, and you only get a subset of the toolbar icons. Once it's done saving, the server bake replaces the preview one and you get the full toolbar.
-
Yes that's what it does. It inlines the client (preview) baked while 'saving' shows, and you only get a subset of the toolbar icons. Once it's done saving, the server bake replaces the preview one and you get the full toolbar.
We knew it did that for the poster, but this seems to indicate that it does that for everyone watching the thread.
-
Wait, does this mean they are dishing out the client baked version while waiting for the server baking to be done?
Maybe they're asking other clients to bake the post? In fact, please let that be what is happening: the alternative — sending out the submitter's baked version to all the other clients — would be a “fascinating” attack vector that quite possibly wouldn't even be logged correctly.
-
I'm still tempted to suggest to them to just store the posts in people's local storage and build a Discourse-based P2P network to retrieve them.
The problem is, I'm afraid someone would take me seriously...
-
No, it's the CookedPostProcessor - the thing responsible for downloading remote images, and passes the post through a parser (Nokogiri) - that's causing this AND the unclosed tag oddities.
It collects image dimensions into a hash keyed by the URL.
-
It collects image dimensions into a hash keyed by the URL.
Which, IIRC, I worked out soon after first reporting this on meta.d
-
Well done. Do you want a cookie?
-
If you're offering…
-
@NedFodder said:
Just like @RaceProUK earlier, I saw it flash to the correct result, then it went back to wrong. Trippy.
Wait, does this mean they are dishing out the client baked version while waiting for the server baking to be done?
Cause that's fracking retarded.
Is that what causes the behaviour where you submit a perfectly cromulent post, and then, several seconds later, the entire post goes skewiff, giving the impression that Discurses was specifically designed just to piss you off? Yeah, it's redarted.
-
-
-
giving the impression that Discurses was specifically designed just to piss you off?
But that's exactly what it was designed for, isn't it?
-
@tar said:
giving the impression that Discurses was specifically designed just to piss you off?
But that's exactly what it was designed for, isn't it?
Now I don't think it was specifically designed for that.
It's pretty good at it, though.
-
-
You're cheating! This is when using images uploaded to Dicksores! External images don't count!
-
No, it's because I specified both height and width.
-
It seems you're correct ...
-
Didn't we work this all out when I first reported this issue?
-
Didn't we work this all out when I first reported this issue?
You expect me to remember something that happened almost three months ago?
-
You're not suggesting you've got more important things to remember?
-
You're not suggesting you've got more important things to remember?
No, just problems with memory overflow.
-
Guess a penguin fell off the ice flow?
-
Penguins aren't mammals?
-
Wut, we now have a "6 days later" divider?
-
I like it; makes it more obvious it's an older thread that's been necro'd ;)
-
i wonder if it switches to months/years for really old necros?
-
I think there's a screenshot around somewhere where it does.
I like it. Bikeshedding with positive results!
-
There should be a "meanwhile..." one for simul-posts.
And maybe a "but the future refused to change..." caption for when you try to edit a post past the edit window.
EDIT: Ooo, how about "douchebag alert" to warn people the following post was written by coding whore.
-
EDIT: Ooo, how about "douchebag alert" to warn people the following post was written by coding whore.
Perfect plan, let's add an 'asshole warning' too
-
@blakeyrat said:
EDIT: Ooo, how about "douchebag alert" to warn people the following post was written by coding whore.
Perfect plan, let's add an 'asshole warning' too
Eh, that sounds like a lot of work—users who care about it can probably just fix it locally using CSS.
-
@Luhmann said:
@blakeyrat said:
EDIT: Ooo, how about "douchebag alert" to warn people the following post was written by coding whore.
Perfect plan, let's add an 'asshole warning' too
Eh, that sounds like a lot of work—users who care about it can probably just fix it locally using CSS.
We have the capability to post a global notice, but I don't think that's going to be terribly useful.
-
Each day you just post a global notice of the dumbest poster for that day. For example, on Monday it might say:
"Warning: Boomzilla is an asshole"
While on Tuesday it might instead say:
"Warning: Boomzilla is an asshole"
And then the dumbest post on Wednesday might prompt it to say:
"Warning: Boomzilla is an asshole"
And the stupidest post on Friday, the one that made all of our IQs drop, would change it to:
"Warning: Boomzilla is an asshole"
etc.
-
I don't really equate being dumb to being an asshole, though. Seems like a flaw in your proposal.
-
He's just still butthurt because his fast booting relies on a Microsoft bug that can destroy data in some cases.
-
Hm, apart from the question of the desirability of the messaging system itself, I think there can be more useful messages. For example, on Monday, it might say:
"Warning: Blakeyrat is being particularly contrary today"
While on Tuesday, it might say:
"Warning: Blakeyrat is being particularly contrary today"
-
It would be more useful if you also got things like:
"Warning: Blakeyrat is being aggressively illiterate today"
so you knew in what way to tweak your baiting of him.
-
The topic on meta has been closed as "This should be fixed".
I don't feel like getting in trouble on meta, and they did a complete reset on test, including the workaround they had for keeping an active account. I'm not creating an account again just to test this there. We'll have to wait until WTDWTF can be updated to verify.
-
-
Sent him a PM to test
-
*looks at the fix implemented*
It took FIVE MONTHS for that simple a fix?
-
Test failed:
Pinged the relevant discodevs to reopen the bug.
-
*looks at the fix implemented*
It took FIVE MONTHS for that simple a fix?
Nope:
Test failed:
Apparently it took longer than that...
-
It looks fixed to me, given the original issue was that all three images would end up the same width, even though it's set different on all three images