Notice: We are now selling NEW Gelbooru Merch~! Domestic shipping is free on all orders! Do you have an artist tag on Gelbooru? Let us know so we can properly credit you!

Ticket Information - ID: #773

ID:Category:SeverityReproducibilityDate SubmittedUpdated By:
0000773Browser Problemsnormalalways10/02/14 10:01PMAnti_Gendou
Assigned to:geltas
View StatusPublic
Target Version:N/A
Summary:notes out of place in google chrome interface
Description:Tested on two PCs and a laptop and with multiple internet service providers.

When using Google Chrome, one of the notes on a post (and almost always only one / perhaps the first one) will collapse to 1X1 pixel and move itself to the upper left corner. If there are multiple notes, the rest will be perfectly normal and behave as they should. If I attempt to edit the broken note, and refresh the page, it will go back to the corner again.

This is very consistent, and happens on multiple computers and laptops, different operating systems, and internet service providers.

But it is specific to Google Chrome. Firefox and IE do not appear to have the issue.
Additional Info:
Jerl replied at 2014-10-03 11:41:52
I wasn't able to reproduce the issue. Can you link a specific example?

Also, do you have any extensions installed in Chrome? Try turning them off and on one at a time to see if any of them might be causing the issue.

Anti_Gendou replied at 2014-10-03 21:27:48
I have only one extension on chrome that is listed; editthiscookie. Turning it off and restarting Chrome did not correct the issue I am seeing.

NSFW examples
The note for the text on the far right is on the left corner of the screen and cannot be moved.

Amusingly, despite having multiple notes, the error did not occur on this next one.

worksafe examples

The correlation I see now is that the broken notes almost always seem to be the note that should be furthest right of the image, yet there are some this won't happen on.

Anti_Gendou replied at 2014-10-03 21:28:20
and now I know that the ID posts work differently here... maybe fix that too.