Badges are a barrier to locations
-
Looks like CSS could be enhanced to handle such cases.
-
I prefer to believe that locations are a barrier to badges.
-
Or maybe there is a missing barrier between the two?
-
Or it's Discourse, where everything's made up and the reasons don't matter!
-
File it on meta.d. I dare you!
-
Maybe later. I'd have to think of how to get badges in a way that permits breakage. If the first line only contains two with a short/middle-length description, you can't overlay it. And without demonstrating it on their own forums quite a bit of the effect would get lost.
-
-
-
I'd have to think of how to get badges in a way that permits breakage. If the first line only contains two with a short/middle-length description, you can't overlay it. And without demonstrating it on their own forums quite a bit of the effect would get lost.
Have a look at my profile (example post). I have added a lengthy location string and it overlaps.
-
Great job, @codlnghorror. You broke the brokenness on my meta.d profile info popup by shortening the combined length of the badges on the top row.
Bug Reporter is shorter than Autobiographer. And that breaks the repro.
Filed under: Belgian Badgers
-
I want to know how the hell the various online shops I went to look for that on have the nerve to charge ~£10 for a mug...
-
Is that before or after shipping is included?
-
-
Thanks, very helpful, would consult again.
-
have the nerve to charge ~£10 for a mug...
Speaking of Google Shopping:
Apparently not only is it ridiculously expensive (at least so I assume - UK prices keep throwing me off), it also fits on a very small person.
Filed under: more songs about bulldogs and food
-
Apparently not only is it ridiculously expensive
That includes personal delivery from the UK to your door. At least it should, for that price.
it also fits on a very small
3x3cm won't even fit Barbie.persondoll.
-
That includes personal delivery from the UK to your door. At least it should, for that price.
Filed under: i'm currently in the UK, so even then it would be ridiculous
-
Another barrier got found, this time involving groups:
-
They really have issues with
layoutsUIsoftware design, don't they?
-
-
They really have issues with
layoutsUIsoftware design, don't they?
Oh, I believe they just don't think about such issues. They develop their stuff without any consideration about layout at all.Now, so do I occasionally, but we have this guy I simply call "The Beautifier" who does his utmost to make the frontend stuff I develop look nice.
If I read their page right, they don't have a dedicated html/css guy on board, so whatever they develop hits the UI straight away. And since they don't seem to think that a dedicated test management is worth its money, any design bugs hit the enduser straight into the face.
-
And since they don't seem to think that a dedicated test management is worth its money, any design bugs hit the enduser straight into the face.
They don't even think of having any sort of live testing before pushing stuff out to the world is worthwhile. I'd be pretty upset with the amount of regressions if I were a paying customer. Because I'm already pretty upset about the amount of regressions as a user of a site for which I don't pay a cent.
-
Because I'm already pretty upset about the amount of regressions as a user of a site for which I don't pay a cent.
i love the regressions - they are how I got all my badgers.
-
They don't even think of having any sort of live testing before pushing stuff out to the world is worthwhile.
We are the live testing I think - one step up from the canary.
-
We are the live testing I think - one step up from the canary.
At least the canary's suffering is over pretty quickly.
-
We are the live testing I think - one step up from the canary.
I don't see any indication that any of that has happened yet. Isn't everyone else basically on the same release plan (dependent upon local admins checking for updates, of course)?
I must say, I have to /spit agree with Jeff that canary is the wrong name for this.
-
Isn't everyone else basically on the same release plan (dependent upon local admins checking for updates, of course)?
The plan discussed in that thread hasn't been implemented yet, but there are different 'releases':
[pjh@sofa discourse]$ grep ^params -A3 /var/docker/containers/app.yml params: ## Which Git revision should this container use? version: HEAD
[pjh@sofa discourse]$ git branch -r origin/HEAD -> origin/master origin/add_search_filter origin/avatar2 origin/category-images origin/ember-perf origin/es6 origin/es6-nonode origin/generated-avatars origin/googlebot origin/import-vbulletin origin/jruby origin/master origin/onebox-gem origin/pluginnew origin/pr/2430 origin/revert-2625-rtl-email origin/tests-passed origin/themer
The only other one I've seen mention of is
tests-passed
. My impression from that topic is that they'll add one or more branches to which site admins can 'subscribe' to.
-
I'm amazed it's taken them this long to get there.
-
-
How was the aftertaste on that one?
I choose to think that we've infected them rather than vice versa. Yes, I know that conversation happened before our main meta.d invasion, but we were hammering on him prior to that. Alternatively, stopped clock.
-
ONEBOXES THAT TELL YOU NOTHING ABOUT THEIR DESTINATION GOGOGO
-
-
Filed
https://bitbucket.org/masamunewos/discoursebugs/issue/27/badges-overlap-location-area-of-usercard