L5 Upgrade page, dark vs light grey circles?

I have noticed when I look at my L5 upgrade page that some of the titles have a black circle next to them, and others are have a grey circle. On my screen, all of the black circles are listed under the Silver package. I currently have the Scholars pkg.
The black circles only appear if I click on the "New to You" . Just curious.
Thanks
Comments
-
Gerald said:
I have noticed when I look at my L5 upgrade page that some of the titles have a black circle next to them, and others are have a grey circle. On my screen, all of the black circles are listed under the Silver package. I currently have the Scholars pkg.
The black circles only appear if I click on the "New to You" . Just curious.
Thanks
I actually made this to respond to a different question, but it does answer yours as well. The black circles represent the currently selected base package. I believe that by default Logos looks at which package you have and suggests an upgrade to a package they consider the next step up for you - but I'm not really sure.
Also note that for some people, not all the circles in a base package are changed to black. This may have to do with how particular browsers handle the background scripts that Logos is using to change the displays. It may also have something to do with how many people are accessing the scripts at the same time on the Logos server.
Anyway, here's my explanation of the screen:
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard,
Thanks for the information
0 -
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
Also note that for some people, not all the circles in a base package are changed to black. This may have to do with how particular browsers handle the background scripts that Logos is using to change the displays. It may also have something to do with how many people are accessing the scripts at the same time on the Logos server.
This was confusing me, too – with Safari 6.0.2 on Mountain Lion, the circles for the selected package do not generally change to black, except for one or two (enough to be puzzling!). I’ve checked with Firefox and that makes much more sense as the grey circles reliably turn black for the selected package.
0 -
Daniel Neades said:Richard DeRuiter said:
Also note that for some people, not all the circles in a base package are changed to black. This may have to do with how particular browsers handle the background scripts that Logos is using to change the displays. It may also have something to do with how many people are accessing the scripts at the same time on the Logos server.
This was confusing me, too – with Safari 6.0.2 on Mountain Lion, the circles for the selected package do not generally change to black, except for one or two (enough to be puzzling!). I’ve checked with Firefox and that makes much more sense as the grey circles reliably turn black for the selected package.
Or... it could be said that Logos did not check their website script to make sure it works on the standard browser of their second largest customer base, including the iPad. [;)]
"I want to know all God's thoughts; the rest are just details." - Albert Einstein
0 -
Patrick S. said:
Or... it could be said that Logos did not check their website script to make sure it works on the standard browser of their second largest customer base, including the iPad.
It also doesnt work in Chrome which represents about 20-30% of users (depending on who you ask), likely because they both use WebKit internally. I wonder if it works on IE 7 or 8 or 9, though not enough to fire up a VM [8-|] (it does work on IE 10 RP)
0 -
Joshua Coady said:
It also doesnt work in Chrome . . .
Just checked on Chrome and it does work perfectly, except for the last section (Feature Distribution), which is exactly the same as how it works on Firefox and IE9 (the only browsers I own).
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Looks like I had the broken version cached in Chrome. Took a hard refresh (Ctrl+F5) but it is now working in Chrome for me as well. That may also fix it in Safari, but I dont use Safari on Mac, so I wouldnt have it cached there and thus cannot test that theory
0