Theme Typography does not work anymore

(@serpentsoft)

Hi Pal,

1. Theme Typography outputs style without selector, The Default Typography only works

2. Custom control convert {>} to equivalent html {gt;} and this is very bad for a lot styles

<style id="tt-font-tt-font-34-font-family" type="text/css"> { font-family: Arvo; }</style>
<style id="tt-font-tt-font-34-font-style" type="text/css"> { font-style: normal; }</style>
<style id="tt-font-tt-font-34-font-weight" type="text/css"> { font-weight: 400; }</style>
<link href="https://fonts.googleapis.com/css?family=Arvo:regular&subset=all" type="text/css" media="all" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Arvo:regular&subset=all" type="text/css" media="all" rel="stylesheet">

Thanks for your great plugin,

Have a nice day.

This topic was modified 9 years, 1 month ago by Serpentsoft.

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Author Sunny Johal
(@sunny_johal)

8 years, 11 months ago
Hi Serpentsoft,
I’ve released a new version of the plugin to prevent style output for controls without a selector.

With regards to your second point. Could you:
- Give me steps to reproduce this issue
- Show me a use case where this is affecting styles
Cheers

Sunny
Thread Starter Serpentsoft
(@serpentsoft)

8 years, 11 months ago

Hi Pal,

1. The recent version doesn’t fix Theme Typography too, If you notice in Inspect Element window the style tags printed without the selectors only font-family

<style id="tt-font-tt-font-77-font-family" type="text/css"> {font-family: 'Arvo'!important; }</style>

2. Try to add a custom selector [.main-menu .nav > li > a] the plugin will convert [>] to [gt;] using a js library in your plugin and of course it’s v. bad because we’re using [>] a lot in css.

Thanks for your awesome work,

Have a nice day.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Theme Typography does not work anymore’ is closed to new replies.

Tags