Previous :: Next Topic |
Author |
Message |
summithound Climbing Connoisseur
Joined: 26 Jul 2004 Posts: 1766 | TRs | Pics Location: Everett, WA |
|
summithound
Climbing Connoisseur
|
Mon Nov 18, 2013 9:44 am
|
|
|
Does this site not support Google Chrome? My trip report shows up clearly using Internet Explorer but it's all messed up with Chrome.
Pain is just weakness leaving the body.
Pain is just weakness leaving the body.
|
Back to top |
|
|
Tom Admin
Joined: 15 Dec 2001 Posts: 17835 | TRs | Pics
|
|
Tom
Admin
|
Mon Nov 18, 2013 1:06 pm
|
|
|
Looks to be a bug in chrome. Displays fine in firefox.
|
Back to top |
|
|
summithound Climbing Connoisseur
Joined: 26 Jul 2004 Posts: 1766 | TRs | Pics Location: Everett, WA |
|
summithound
Climbing Connoisseur
|
Mon Nov 18, 2013 1:06 pm
|
|
|
Great; Thanks Tom. I'm glad it's not just me!
Pain is just weakness leaving the body.
Pain is just weakness leaving the body.
|
Back to top |
|
|
Dalekz Member
Joined: 01 Mar 2002 Posts: 487 | TRs | Pics
|
|
Dalekz
Member
|
Mon Nov 18, 2013 2:11 pm
|
|
|
I use Google Chrome and everything seems fine. Maybe something is wrong with yours
|
Back to top |
|
|
Tom Admin
Joined: 15 Dec 2001 Posts: 17835 | TRs | Pics
|
|
Tom
Admin
|
Mon Nov 18, 2013 5:25 pm
|
|
|
I ran some tests with a smaller image set (see below). When I hit refresh, Chrome displays correctly about 10% of the time. 90% of the time it displays things out of order. This makes no sense. It should repeat the same behavior 100% of the time. I downloaded the page to my local machine and turned off the internet connection to rule out a virus on the server, flaky internet connection, etc. but duplicated the exact same phenomenon. I think this is a Chrome bug and not something on our end. I also tried clearing cache, resetting Chrome to defaults, etc. to no avail. I would try downloading the most recent version of Chrome to see if it fixes the issue.
Test:
Image A should follow:
A
Image B should follow:
B
Image C should follow:
C
Image C should be above.
|
Back to top |
|
|
summithound Climbing Connoisseur
Joined: 26 Jul 2004 Posts: 1766 | TRs | Pics Location: Everett, WA |
|
summithound
Climbing Connoisseur
|
Mon Nov 18, 2013 5:28 pm
|
|
|
Tom, I have the most recent version of Chrome installed on my machine. One odd thing, it appears correctly on my Android phone which also uses Chrome.
Pain is just weakness leaving the body.
Pain is just weakness leaving the body.
|
Back to top |
|
|
Tom Admin
Joined: 15 Dec 2001 Posts: 17835 | TRs | Pics
|
|
Tom
Admin
|
Mon Nov 18, 2013 6:09 pm
|
|
|
I changed a few things around and Chrome seems to be behaving now. Let me know if you see other strange stuff happening. What I changed shouldn't have made any difference.
Edit: Grr, seems to be back to misbehaving. Completely random.
|
Back to top |
|
|
summithound Climbing Connoisseur
Joined: 26 Jul 2004 Posts: 1766 | TRs | Pics Location: Everett, WA |
|
summithound
Climbing Connoisseur
|
Mon Nov 18, 2013 6:12 pm
|
|
|
Yep, still looks messed up on my end.
Pain is just weakness leaving the body.
Pain is just weakness leaving the body.
|
Back to top |
|
|
Magellan Brutally Handsome
Joined: 26 Jul 2006 Posts: 13116 | TRs | Pics Location: Inexorable descent |
|
Magellan
Brutally Handsome
|
Mon Nov 18, 2013 10:21 pm
|
|
|
Weird.
|
Back to top |
|
|
Tom Admin
Joined: 15 Dec 2001 Posts: 17835 | TRs | Pics
|
|
Tom
Admin
|
Mon Nov 18, 2013 11:41 pm
|
|
|
OK, figured out the problem. For each picture we call a javascript function to check the remaining width on the screen before we display it to figure out whether we need to wrap / start a new row. It seems Chrome does not necessarily wait for each call to finish before it starts writing the rest of the output so things get jumbled.
|
Back to top |
|
|
summithound Climbing Connoisseur
Joined: 26 Jul 2004 Posts: 1766 | TRs | Pics Location: Everett, WA |
|
summithound
Climbing Connoisseur
|
Mon Nov 18, 2013 11:47 pm
|
|
|
Awesome, thanks! Let me know when the fix is in place and I'll remove that obnoxious disclaimer from my trip report. I'm surprised I was the first to notice this issue.
Pain is just weakness leaving the body.
Pain is just weakness leaving the body.
|
Back to top |
|
|
Tom Admin
Joined: 15 Dec 2001 Posts: 17835 | TRs | Pics
|
|
Tom
Admin
|
Tue Nov 19, 2013 1:30 pm
|
|
|
OK, put in a fix that seems to make Chrome behave 100% of the time now. Let me know if you experience any other issues.
|
Back to top |
|
|
nuclear_eggset Member
Joined: 02 Jul 2006 Posts: 2206 | TRs | Pics Location: Eastside |
May I just say that this thread proves than Tom is an awesome admin!
|
Back to top |
|
|
iron Member
Joined: 10 Aug 2008 Posts: 6391 | TRs | Pics Location: southeast kootenays |
|
iron
Member
|
Wed Dec 11, 2013 1:45 pm
|
|
|
HJT wrote: | I've never had any problems with Chrome and NWHikers. |
nuclear_eggset wrote: | May I just say that this thread proves than Tom is an awesome admin! |
|
Back to top |
|
|
moonspots Happy Curmudgeon
Joined: 03 Feb 2007 Posts: 2456 | TRs | Pics Location: North Dakota |
|
moonspots
Happy Curmudgeon
|
Thu Jan 16, 2014 6:01 am
|
|
|
Tom wrote: | OK, figured out the problem. For each picture we call a javascript function to check the remaining width on the screen before we display it to figure out whether we need to wrap / start a new row. It seems Chrome does not necessarily wait for each call to finish before it starts writing the rest of the output so things get jumbled. |
Wow, how on earth does one figure that kind of thing out???
I can figure out multitudes of electronic mis-behaviors, but soft/firmware issues befuddle me mostly.
Thanks for all the effort!
"Out, OUT you demons of Stupidity"! - St Dogbert, patron Saint of Technology
"Out, OUT you demons of Stupidity"! - St Dogbert, patron Saint of Technology
|
Back to top |
|
|
|