Report site bugs here

@Barhandar  
Yeah, I think the same usually, why change when it works?, but derpibooru do it a lot so I stopped critiquing it.

Grrr fine. Not a single source mentioned that these other browsers had horrendous flexbox bugs as well.
 
Reverted. Blame IE.

I am also a Pale Moon user. It’s nice to see the site looking good again.  
BTW, Pale Moon 26.1.1 was released less than 3 weeks ago. It’s not an “old” browser.

@Softy  
It only supports an older version of the specs that Firefox has long since supported, hence it is old (even if recently released).

Palemoon is not one of the browsers we support - from a HTML/CSS specification compliance perspective it’s well behind the times. We only support reasonably modern browsers (from a spec compliance perspective) as it lets us use features that improve performance, complexity and so on for the majority of users who use modern browsers. Basically, for the sake of the 99% of users who will benefit, we’ll break the 1%, sure.

@Barhandar  
Flexbox is not bleeding edge, Palemoon is just old and certain other browsers don’t implement it correctly.
 
In regards to what happened, basically, a “sticky” footer is a highly-sought-after feature of website design. The original CSS I used for it didn’t work quite right in IE, but the fix I came up with sort of worked (footer wasn’t sticky in IE, but nothing would break in old browsers).  
More recently, I was informed of an alternate fix for IE that should allow for a sticky footer in all the browsers we support; unfortunately, it turns out that it breaks in Safari (and Palemoon), so we went back to the original fix.
 
Also, we do not actually support Palemoon. We’ve run into serious issues with it in the past for visual image comparison for duplicates (which we plan on making public) that cannot be fixed.
 
@Softy  
Version 26.1.1 seems to actually implement flexbox correctly for our purposes. The trouble, generally, is that Palemoon isn’t quite caught up because it’s based on old Firefox versions with stuff backported.

>>1060410 says it’s hidden by my complex filters but none of the other pages of the comic that have the tags “questionable” and “comics:anon’s pie adventure” are spoilered…
 
I have in my complex filters to completely unhide any questionable images that have the tag “comic:anon’s pie adventure”
 
http://i.imgur.com/Q1qHOkw.png

@Rainboom Dash  
I would suggest extrapolating on how you wrote such an exception to your complex filters, because as far as I’m aware we have no such thing. Unless you added “-(questionable AND comic:anon’s etc)” to the end of all your complex filters, I’m going to go out on a limb and say that particular image is triggering a different filter than what I presume is a fairly global filter on questionable rated images.

@Keith Mowz  
I think he just made a typo.
 
@Rainboom Dash  
Complex filter looks correct, I think this is a bug of some kind.

@Keith Mowz  
I’ve helped him with his filter and I understand boolean logic fairly well, but as far as I can tell it shouldn’t be doing that.

The image’s indexing was wrong, saving tags with no changes fixed it.

@liamwhite1
 
Said bug is still persisting. i know this is not a Firefox-only problem. i tried to do the same thing on Chrome and it yielded the same results.

The alphabetical tag ordering in the page title and thumbnail mouseover doesn’t seem to quite match the one in the actual page concerning special characters like asterisks.  
For example, in this one:  
>>1074066tthe mouseover text lists the “*you’re” tag last, seeming to ignore the asterisk, but the actual page puts the asterisk first in alphabetical ordering.
 
 
While we’re on this topic, some of LoreHoshiko’s old images seem to have an old version of their artist tag in the mouseover text which has since been aliased and doesn’t actually exist anymore:  

@SuperSupermario24  
Probably easy to fix, but low priority.
 
Indexing, probably from a time when aliasing wasn’t working quite right. I’ve reindexed the tags.

About that bug i was telling you about, it looks like it’s gone now. what was it?
 
@SuperSupermario24
 
Not only there, but in other images of artists with aliases. i see a lot of old xishka images in which the mouseover text still reads “artist:cherkivi”

@Mildgyth  
Maybe liam fixed it while he was messing with the tag CSS. I don’t know.

@Princess Luna  
*JS

Downtime was postgres shitting itself. Apologies.

What the butt happened to upvotes galore and downvotes galore? I saw a couple of days ago that some similar “this image has a large number of upvotes” tags were being merged, but not having any tag at all to indicate the concept seems extreme.

@TexasUberAlles  
I’ve heard talk of the staff just killing off those particular tags entirely for a while now; maybe they finally did it

@TexasUberAlles  
they’re completely gone.
 
thank fucking god

@TexasUberAlles  
This thread here is basically it.

@TexasUberAlles  
Those tags are not to be used anymore, you can look for the same images just by setting the upvote count to +250 or whatever you wish.

@Marukomuru  
This thread here is basically it  
 
Man, if that had been a bomber it could have spent the last four months laying waste to all my major cities, sheesh.

I tried to edit a message and got this
 

 
I realize it’s because I waited too long to edit the message.. but maybe it should say something else besides just “you might’ve hit a bug”?
 
Just a suggestion
 
I understand that being able to edit your own comments is something new and still being worked on