On Thu, Mar 27, 2014 at 12:34 PM, Tom Livingston wrote:
>
> I was doing this simple test with google fonts (via @import method).
>
> body{
> font-family: $roboto;
> }
>
> .bold{
> font-weight: 500;
> }
>
> Hi there bolded text
> I'm bold
>
> The strong tag above was rendering wrong in FF
On Thu, Mar 27, 2014 at 2:44 PM, Jukka K. Korpela wrote:
> 2014-03-27 18:34, Tom Livingston wrote:
>
> I was doing this simple test with google fonts (via @import method).
>>
>> body{
>> font-family: $roboto;
>> }
>>
>> .bold{
>> font-weight: 500;
>> }
>>
>
> I suppose you are using som
On Thu, Mar 27, 2014 at 3:25 PM, Eric wrote:
> Yes, I realize that. I was just checking to see if a different CSS approach
> might be used.
>
> > On March 27, 2014 at 2:53 PM Philip Taylor wrote:
> >
> >
> >
> >
> > Eric wrote:
> >
> > > You're not using the strong tag for styling are you?
> >
>
This (small font families...few included weights) and the fact that the bulk of
the Yahoo Fonts are not the highest quality is the reason I moved to Typekit.
Personally I'll do anything to avoid a UA's faux bold and italic rendering.
If you need to use Google Fonts there are a couple of good artic
Yes, I realize that. I was just checking to see if a different CSS approach
might be used.
> On March 27, 2014 at 2:53 PM Philip Taylor wrote:
>
>
>
>
> Eric wrote:
>
> > You're not using the strong tag for styling are you?
>
> I very much suspect that the browser neither knows nor cares
> why an
On 3/27/14, 9:34 AM, Tom Livingston wrote:
I was doing this simple test with google fonts (via @import method).
body{
font-family: $roboto;
}
.bold{
font-weight: 500;
}
Hi there bolded text
I'm bold
The strong tag above was rendering wrong in FF and Chrome. FF was
'double-bolding' t
Eric wrote:
You're not using the strong tag for styling are you?
I very much suspect that the browser neither knows nor cares
why any particular tag has been used, Eric; it almost certainly
renders the tagged element identically, regardless of the
motivation for the tag's use.
Philip Taylor
2014-03-27 18:34, Tom Livingston wrote:
I was doing this simple test with google fonts (via @import method).
body{
font-family: $roboto;
}
.bold{
font-weight: 500;
}
I suppose you are using some special tools that convert that $roboto to
a real name. But how do you refer to the fo
Tom,
You're not using the strong tag for styling are you?
> On March 27, 2014 at 12:34 PM Tom Livingston wrote:
>
>
> I was doing this simple test with google fonts (via @import method).
>
> body{
> font-family: $roboto;
> }
>
> .bold{
> font-weight: 500;
> }
>
> Hi there bolded text
> I'm bold
>
> Thanks Isabel. All i can say is I'm glad it isn't a case of me just being
> tick-headed. It's not just me.
>
>
>
Er, I mean thick-headed.
--
Tom Livingston | Senior Front-End Developer | Media Logic |
ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com
___
On Thu, Mar 27, 2014 at 2:04 PM, Isabel Santos wrote:
> Hi Tom,
>
> font-weight:500 means semi-bold, default for is bold, so I gess
> you need to add that extra rule
> strong {
> font-weight: 500;
> }
> you can take a look at:
>
> http://elliotjaystocks.com/blog/font-weight-in-the-age-of-web
Hi Tom,
font-weight:500 means semi-bold, default for is bold, so I gess
you need to add that extra rule
strong {
font-weight: 500;
}
you can take a look at:
http://elliotjaystocks.com/blog/font-weight-in-the-age-of-web-fonts/
and
http://css-tricks.com/watch-your-font-weight/
hope it helps
I was doing this simple test with google fonts (via @import method).
body{
font-family: $roboto;
}
.bold{
font-weight: 500;
}
Hi there bolded text
I'm bold
The strong tag above was rendering wrong in FF and Chrome. FF was
'double-bolding' the text, and Chrome showed odd char spacing.
A
13 matches
Mail list logo
