I'd like to see some time in future the ability so simply scroll through the pages (the content loads as you scroll) Rather than navigating by clicking on the page number and the next page link, that method is more modern and found on many sites already.
It would also be pretty cool if a users browsing progress was saved (shown as lines or blocks on a bar, new unseen content colored differently on top for example) so you could tell which areas of content you've already looked at (and maybe where you could look further) and maybe even what's been downloaded by yourself.
I'd like to see some time in future the ability so simply scroll through the pages (the content loads as you scroll) Rather than navigating by clicking on the page number and the next page link, that method is more modern and found on many sites already.
So I'm getting a NoMethodError exception when I'm in the appeals section, if I search using one term, then attempt to go to page 2. It's replicable (for me at least). Just put the word 'awesome' into the reason search bar, and then try going to page 2.
A couple of months ago, Moonspeaker discovered a bug in note rendering which could cause a browser crash, or a browser tab to become unresponsive (first mentioned in forum #104585). Later, we discovered that the crash is triggered by elements within the note trying to render wider than the div.note-body that contains them, i.e., having a horizontal margin value less than -4px. At the time, we decided simply not to use such margin values, but this doesn't help any user who may discover this bug independently without having been part of that discussion.
Today, I discovered that changing the overflow value for div.note-body to visible averts the bug entirely. In addition, it allows for greater versatility for note editors. For example, I would be able to put the red shadows of the notes in the center panel of post #1996319outside of the note container, and have them render directly over the image.
e: actually, it seems my browser is inserting most of the linebreaks in that file automatically. Alternatively, it's at application-542bc92cd1ffbdfa3583abb8c732555d.css:5:42498 or the third instance in the file of the phrase "overflow:auto"
A couple of months ago, Moonspeaker discovered a bug in note rendering which could cause a browser crash, or a browser tab to become unresponsive (first mentioned in forum #104585). Later, we discovered that the crash is triggered by elements within the note trying to render wider than the div.note-body that contains them, i.e., having a horizontal margin value less than -4px. At the time, we decided simply not to use such margin values, but this doesn't help any user who may discover this bug independently without having been part of that discussion.
Today, I discovered that changing the overflow value for div.note-body to visible averts the bug entirely.
Huh? But I already fixed that bug over a month ago.
It's still happening for you? What post is it happening on?
Ha! I was being so careful not to crash my browser, but neglected to check whether the bug was already fixed.
Anyway, the request still stands, but as a feature request rather than a bugfix. It would be cool to be able to get out of the bounds of the note container.
Anyway, the request still stands, but as a feature request rather than a bugfix. It would be cool to be able to get out of the bounds of the note container.
Changing to overflow:visible allows note editors to place things outside the note body. This could be used maliciously. For example someone could place a fake login link in place of Danbooru's real one, which leads to a site that looks like Danbooru and tries to steal people's login information.
Actually it seems slower with lower posts per page. With watarase_jun limit:50 (what I use) it works fine, but watarase_jun limit:20 times out. Pretty strange, but I recommend just using a higher limit to get around it.
I just noticed the "Dmail filter" field in "Advanced settings". For some reason, it contained my user name ("flopsy" (without quotes)), even though I have never entered that or any other value. I tried deleting "flopsy" and then clicking "Submit", but when I went back to "Advanced settings", the field still contained "flopsy". Then I tried replacing "flopsy" with "boners" and clicking "Submit" again. Firefox immediately opened a notice asking me whether I wanted it to remember the password for "boners" on donmai.us, as if I had just entered a new username-password combination. Uh, no? This time, the field still contained "boners" when I went back to check. Replacing "boners" with "boner" also worked and this time there was no password notice. When I deleted "boner" and submitted an empty field, "flopsy" came back.
Is this intended behavior? If so, why?
Edit: I inspected the input element for the field. The "flopsy" string is not actually there in the HTML. The values I have entered myself ("boners", etc.) are there. Presumably, Firefox is somehow mistaking the field for a username field and helpfully inserts what it thinks is the appropriate value.
Edit 2: When I submit the "Advanced settings" form with the auto-inserted "flopsy" value in the filter field, the "flopsy" value is present in the HTML the next time I view the form. If this happens for all Firefox users, then people could end up inadvertently filtering out any dmail that contains their username.
