I've tried several system fonts (installed with Windows), the google fonts 
that I have embedded in my TW as well as exactly what you had and none of 
them had any effect. It's as if that particular setting is being completely 
ignored. I upgraded my TW via the upgrade website and saved as a new file 
so as not to mess up my original.  What's interesting is that areas of my 
TW that have the font specified via custom stylesheet are working just 
fine. It's only the stuff that uses the control panel / theme tweaks 
setting.

On Monday, November 30, 2020 at 9:55:36 PM UTC-7 [email protected] wrote:

> @History Buff I am not able to re-create the problem.
>
> At tiddlywiki.com/prerelease I changed the font family via theme tweaks 
> to:
> "sans-serif, "Apple Color Emoji", "Segoe UI Emoji" and the changes are 
> applied immediately.
>
> Can you specify the exact font-family you are trying to use and that the 
> problem exists on the current version at 
> https://tiddlywiki.com/prerelease/
> Thank you.
>
> On Monday, November 30, 2020 at 11:11:15 PM UTC+1 History Buff wrote:
>
>> I am changing the font family via the Control Panel and theme tweaks. 
>> That's why I am a little confused on why that would change behavior.
>>
>> On Monday, November 30, 2020 at 3:01:02 PM UTC-7 [email protected] 
>> wrote:
>>
>>> @History Buff :
>>>
>>> are you changing your font family via the Control Panel and the  
>>> $:/themes/tiddlywiki/vanilla/settings/fontfamily  tiddler? 
>>> That should override the font specified by normalize. 
>>>
>>> Or are you just specifying a different font-family in a stylesheet 
>>> tiddler?
>>>
>>> On Monday, November 30, 2020 at 10:36:35 PM UTC+1 History Buff wrote:
>>>
>>>> All,
>>>>
>>>> Admittedly, I've only tried to play with it for about half an hour, but 
>>>> I noticed that the font-family from my theme tweaks was no longer being 
>>>> used. I see that vanilla base was modfied to include the following which 
>>>> seems to be causing my issues:
>>>>
>>>> /** Improve consistency of default fonts in all browsers. (
>>>> https://github.com/sindresorhus/modern-normalize/issues/3) */ body { 
>>>> font-family: system-ui, -apple-system, /* Firefox supports this but not 
>>>> yet 
>>>> `system-ui` */ 'Segoe UI', Roboto, Helvetica, Arial, sans-serif, 'Apple 
>>>> Color Emoji', 'Segoe UI Emoji'; } 
>>>>
>>>> If I use the inspect tool with Chrome to take that out, all goes back 
>>>> to normal.  
>>>>
>>>> On Monday, November 30, 2020 at 2:15:16 PM UTC-7 coda coder wrote:
>>>>
>>>>> There's a lot to be excited about in this release, far too many things 
>>>>> to mention here. But this... I'm unashamedly ecstatic about ...
>>>>>
>>>>> https://tiddlywiki.com/prerelease/#EventCatcherWidget
>>>>>
>>>>> Thanks Saq!
>>>>>
>>>>> On Monday, November 30, 2020 at 10:48:13 AM UTC-6 [email protected] 
>>>>> wrote:
>>>>>
>>>>>> Many blessings to Jeremy and the contributors of the community.
>>>>>> Anxiously awaiting the release.
>>>>>>
>>>>>> Regards all,
>>>>>> Julio
>>>>>>
>>>>>> On Monday, November 30, 2020 at 10:58:27 AM UTC-5 TiddlyTweeter wrote:
>>>>>>
>>>>>>> Jeremy ...
>>>>>>> * The beginnings of support for switchable page templates (referred 
>>>>>>> to as layouts), which will give us a route to introduce a more modern 
>>>>>>> alternative layout
>>>>>>>
>>>>>>> I noticed that. I think its a very good step. Alongside what PMario 
>>>>>>> is doing to greatly expand WikiText, the fluidity of the visuals in TW 
>>>>>>> will 
>>>>>>> being to approach the flex the more programmatic aspects have. I 
>>>>>>> seriously 
>>>>>>> believe "looks" matter. They are never really passive. They help shape 
>>>>>>> good 
>>>>>>> realization.
>>>>>>>
>>>>>>> Thanks!
>>>>>>> Best wishes
>>>>>>> TT
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7f3d40a6-0011-4f11-add6-569841b12fb3n%40googlegroups.com.

Reply via email to