-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flashing, resizing at http://geodata.tufts.edu/ #6
Comments
Hi Daniel, Can you give some more specifics about your machine (OS) and your chrome install (what plugins/extensions are you using)? I don't get the same results for the same version of Chrome for OS 10.8 or for Windows 7. Does there seem to be some series of actions that triggers this behavior? Other possibilities:
|
Hi Chris, This just happened for our site. I suspect it is a sizing issue and it Thanks for looking into this. I'll let you know if I see it again. Daniel On Tue, Mar 5, 2013 at 12:53 PM, chrissbarnett [email protected]:
|
I just noticed this bug report here. I saw this behavior elsewhere, as well. In my case, at least, this was caused by Google's "Do you want me to translate this" message that shows up when Chrome thinks the page is in another language. This resizes the browser window, which causes another search to happen, which resets the search results, which causes the translate message, etc. I could reproduce it by finding a search results that had titles in another language. The fix that worked for me was to add:
to the head of the page. This suppresses the message in Chrome, though it's not specifically documented, so it feels like a bit of a hack and kind of ham-handed. It would also probably be possible to fix it by throttling the function that does the searching. |
Using Chrome version 25.0.1364.152, the Tufts interface seems to act like the user is resizing with the map and most icons on the right side of the map moving along with the number of results moving from 24 to 25 per page. I just upgraded Chrome to see if this issue was related to the version but the problem remains.
The text was updated successfully, but these errors were encountered: