On Thu, Jan 22, 2015 at 11:39 PM, worik wrote:
> Friends
>
> I have problems getting my sizing of divs correct.
>
>
> Given the HTML:
>
> A B C
> E F G
>
>
> .A {
> width=100%;
> border:2px solid blue;
> }
> .B {
> width=50%;
> border:1px solid red;
> }
>
> I want to make the
Friends
I have problems getting my sizing of divs correct.
Given the HTML:
A B C
E F G
.A {
width=100%;
border:2px solid blue;
}
.B {
width=50%;
border:1px solid red;
}
I want to make the nested div half the width of the outer div. But they
both expand to the fill width.
jan 23 2015 03:36 gpalz :
> I have a client who wishes to have body copy as Helvetica Light.
And the client is willing to pay for the proper licensing? Or for your time to
dig up free alternatives?
$font-face as have been suggested works then, but make sure to supply
alternatives in your fon
> Le 23 janv. 2015 à 11:36, gpalz a écrit :
>
> I have a client who wishes to have body copy as Helvetica Light. I'm on a pc
> and have Helvetica LT Std. The following font-weights produce the following
> results:
>
> Anything between 100-500/Lighter appears as normal. 600 and 700 appears as
I have a client who wishes to have body copy as Helvetica Light. I'm on
a pc and have Helvetica LT Std. The following font-weights produce the
following results:
Anything between 100-500/Lighter appears as normal. 600 and 700 appears
as bold and 900 appears as Black.
How does one targe
Howdy George,
~~~
Thursday, January 22, 2015, 9:36:15 PM (USA 'Somewhere on-the-road time-zone'),
you wrote the message that appears below.
My reply appears here and/or interspersed within your message.
~~~
> I have a client who wishes to have body copy as Helvetica Light. I'm on
> a pc and h
I have a client who wishes to have body copy as Helvetica Light. I'm on
a pc and have Helvetica LT Std. The following font-weights produce the
following results:
Anything between 100-500/Lighter appears as normal. 600 and 700 appears
as bold and 900 appears as Black.
How does one target Ligh
On Jan 22, 2015, at 10:38 AM, Tom Livingston wrote:
> On Thu Jan 22 2015 at 11:02:52 AM Chris Rockwell
> wrote:
>
>> Here is an old article on z-index which may provide some insight:
>> http://yagudaev.com/posts/getting-reliable-z-index-cross-browser/
>>
>> Specifically:
>>
>> *Another proble
My apologies if this annoys anyone, but it seemed to be worth sharing...
-- Forwarded message -
From: Steven Champeon
Date: Thu Jan 22 2015 at 1:19:31 PM
Subject: [WD]: FW: Molly needs you!
To:
Folks, Molly needs your help. Please be generous, as she has been for
her many years
It appears that the addition of this:
-webkit-transform: translate3d(0,0,0);
fixes the Safari issue.
That fix was mentioned in one of the StackOverflow threads I saw while
looking into this. Odd that adding z-index didn't work as it did on my
end, as well as removing `position:relative`. Oh wel
On Thu Jan 22 2015 at 11:38:00 AM Tom Livingston wrote:
> On Thu Jan 22 2015 at 11:02:52 AM Chris Rockwell
> wrote:
>
>> Here is an old article on z-index which may provide some insight:
>> http://yagudaev.com/posts/getting-reliable-z-index-cross-browser/
>>
>> Specifically:
>>
>> *Another probl
On Thu Jan 22 2015 at 11:02:52 AM Chris Rockwell
wrote:
> Here is an old article on z-index which may provide some insight:
> http://yagudaev.com/posts/getting-reliable-z-index-cross-browser/
>
> Specifically:
>
> *Another problem is that if the element has no z-index, but its container
> does, t
Here is an old article on z-index which may provide some insight:
http://yagudaev.com/posts/getting-reliable-z-index-cross-browser/
Specifically:
*Another problem is that if the element has no z-index, but its container
does, the z-index returned would be auto in all browsers other than IE7,
whic
I think if you add a z-index to everything that is position:relative it
will solve the issue (.circle-button, .plant-it). It doesn't appear that
those need position:relative anyway.
I'm not sure why this is happening, but there seems to be a lot of threads
in google about safari z-index issues.
Tom Livingston wrote:
With respect, the code that the validator doesn't like or understand is
necessary and the issue isn't showing up on other pages of the site with
the same stylesheet.
Fair enough. But I personally make it a rule never to investigate the
mis-behaviour of a page that fai
On Thu Jan 22 2015 at 9:51:14 AM Philip Taylor wrote:
>
>
> Tom Livingston wrote:
> > OK. I managed to recreate the issue on a sample page:
> > http://proof.mlinc.com/tl/cssd/
> >
> > There are 55 known validation errors which are related to 3rd party code
> as
> > well as M$ gradient filter code
Tom Livingston wrote:
OK. I managed to recreate the issue on a sample page:
http://proof.mlinc.com/tl/cssd/
There are 55 known validation errors which are related to 3rd party code as
well as M$ gradient filter code. I can live with them unless they are
actually causing my issue.
So why not
OK. I managed to recreate the issue on a sample page:
http://proof.mlinc.com/tl/cssd/
There are 55 known validation errors which are related to 3rd party code as
well as M$ gradient filter code. I can live with them unless they are
actually causing my issue.
The issue appears in Mac Safari Versio
I will try to see if I can create something to post that will recreate the
issue.
.wrap is relative positioning.
Chris, it does work but I think it looks great! ;-)
On Wed Jan 21 2015 at 11:00:52 PM Chris Rockwell
wrote:
> This is pretty ugly, but it works on Safari MAC :
> http://codepen.io/c
19 matches
Mail list logo