Hello Josh, I agree with you (I don't know if my English translation was the 
most correct 😝)
No problem, I'm waiting.
I'll try to find some time to investigate the combobox issue.

Best regards.

Hiedra

-----Mensaje original-----
De: Josh Tynjala <joshtynj...@bowlerhat.dev> 
Enviado el: viernes, 21 de marzo de 2025 15:22
Para: dev@royale.apache.org
Asunto: Re: royale.apache.org website not loading fonts either

I have not yet had time to review your changes. After I do, I will upload TDJ. 
My message was intended to acknowledge your request to review your work on TDJ.

--
Josh Tynjala
Bowler Hat LLC
https://bowlerhat.dev/


On Fri, Mar 21, 2025 at 3:08 AM Maria Jose Esteve <mjest...@iest.com> wrote:

> @Josh, aren't my changes correct in TDJ?
> If they're not correct, let me know and I'll fix them.
> I made a bunch of changes last week, and they're still waiting for 
> someone more experienced than me to validate them so we can merge them 
> into royale-asjs.
>
> Hiedra
>
> -----Mensaje original-----
> De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: jueves, 20 de 
> marzo de 2025 23:55
> Para: Apache Royale Development <dev@royale.apache.org>
> Asunto: Re: royale.apache.org website not loading fonts either
>
> royale-website and royale-docs successfully updated to remove external 
> fonts, styles, and scripts. That's all I have time for today.
>
> I have not yet uploaded the new build of TourDeJewel to the website, 
> but I will as soon as I get a chance.
>
> I will also update ASDoc, and some other Jewel-based examples we have 
> on the website.
>
> --
> Josh Tynjala
> Bowler Hat LLC
> https://bowlerhat.dev/
>
>
> On Thu, Mar 20, 2025 at 9:11 AM Josh Tynjala 
> <joshtynj...@bowlerhat.dev>
> wrote:
>
> > I just loaded our main royale.apache.org website, and I observed 
> > that the fonts were failing to load there too, just like Tour de Jewel.
> >
> > It's the same issue. The stricter security policy is preventing us 
> > from using Google Fonts from fonts.gstatic.com.
> >
> > It was falling back to the browser's default serif font, which 
> > wasn't ideal. I just pushed a quick fix to fall back to sans-serif instead.
> > However, we'll either need to move the fonts to our server (if the 
> > license and ASF policy permits), or we'll need to switch to other fonts.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC
> > https://bowlerhat.dev/
> >
>

Reply via email to