gsymon
September 24, 2014, 8:19am
1
I’m trying to use the ScriptyLightBox3 action and am finding that if CSS Menus are present ‘behind’ the pop-out window, then they show through in the image. If the window is scrolled so that the CSS Menus are no longer directly behind the pop-out, then they are not seen.
I realise that compatibility is for FW6, but am wondering if this is another issue and if I can fix it in some other way?
You can see the effect here (the top 4 images have the ScriptyLightBox3 action applied)
http://test-1.grantsymon.com/prints.html
freewaytalk mailing listhttp://freewaytalk.net/person/options
The DIV item named CSSMenu has a z-index of 9999 while the lightbox has one of 1000.
So if you set the CSSMenu to z-index:999 (extended dialogue DIV style tab) it should be good.
Cheers
Thomas
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 8:51am
3
Hi Thomas,
Thanks for the help.
I tried 999 and 99, but it doesn’t fix it.
(I notice in another thread, that you mention the Clearfix action in relation to z-index. I am using the Clearfix action. Could this have any bearing on the problem?)
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 8:52am
4
Should have mentioned I updated the page with z-index 99 if you want to take a look.
freewaytalk mailing listhttp://freewaytalk.net/person/options
I am still seeing your CSS Menu with
#CSSMenu {
width: 100%;
z-index: 9999;
David
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 10:05am
6
Thanks Dave … I’m learning slowly.
I’d changed the Master, but somewhere along the line, the child page had lost it’s association.
All good now.
freewaytalk mailing listhttp://freewaytalk.net/person/options
You also seem to have a duplication in your font-weight declaration for LogoTitle
.LogoTitle {
color: #4c4c4c;
font-family: 'Source Sans Pro', sans-serif;
font-weight: 300;
font-size: 54px;
font-weight: 300;
}
D
freewaytalk mailing listhttp://freewaytalk.net/person/options
… and I furthermore tend to say, that this line of code should fix another font-problem:
<link href='http://fonts.googleapis.com/css?family=Source+Sans+Pro:300,400' rel='stylesheet' type='text/css'>
For Font strategy in general, I once started a couple of screencasts which you could include into your learning curve as well (if you want):
http://www.kimmich-digitalmedia.com/videos/013_thecodingepisodes_part6_the-paragraph
Cheers
Thomas
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 11:46am
9
Thanks Dave.
Could that be because the I included the weight in the Font Sets - alternative?
freewaytalk mailing listhttp://freewaytalk.net/person/options
Could that be because the I included the weight in the Font Sets - alternative?
Hard to tell but appears to be applied twice in the .LogoTitle style itself
D
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 12:01pm
11
Thanks Thomas.
You may recall that I couldn’t get SourceSansLight to work for me when using that line of code. So I included SourceSansLight as a google font and I have this line of code :
Is this a mistake?
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 12:02pm
12
Forgot to mention … I already watched your video and am now using Styles as you suggest.
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 12:02pm
13
Be good if we could edit posts …
freewaytalk mailing listhttp://freewaytalk.net/person/options
On 24 Sep 2014, 12:01 pm, grantsymon wrote:
Thanks Thomas.
You may recall that I couldn’t get SourceSansLight to work for me when using that line of code. So I included SourceSansLight as a google font and I have this line of code :
Is this a mistake?
Well - i’d say yes cause you got an error on your page (Status 400 - Bad request). Called your page in FF on PC and the FONT won’t display.
Cheers
Thomas
freewaytalk mailing listhttp://freewaytalk.net/person/options
gsymon
September 24, 2014, 12:25pm
15
On 24 Sep 2014, 12:13 pm, Thomas Kimmich wrote:
Well - i’d say yes cause you got an error on your page (Status 400 - Bad request). Called your page in FF on PC and the FONT won’t display.
OK, Thanks for the pointer. I’ve changed the code and it is working for me now.
Hopefully PC users can join the party.
freewaytalk mailing listhttp://freewaytalk.net/person/options
I would be using
And then define the font weights in the styles something like
body {
font-family: 'Source Sans Pro', sans-serif;
font-weight: 300;
}
h1 {
font-family: 'Source Sans Pro', sans-serif;
font-weight: 400;
}
Example here: http://www.deltadesign.co/FW7Test/sourcesanspro.html
D
freewaytalk mailing listhttp://freewaytalk.net/person/options
Hopefully PC users can join the party.
Looking good now.
(Do people really still use those things?
Apparently yes. In the office, I’ve got two machines:
My Mac for graphic design and a PC where the invoicing program and a 3D bath planning software is hosted. I tried them both on my mac as well but especially the 3D app was soooooo slow.
Cheers
Thomas
freewaytalk mailing listhttp://freewaytalk.net/person/options
