URI:
   DIR Return Create A Forum - Home
       ---------------------------------------------------------
       Create A Forum - Support Forums
  HTML https://support.createaforum.com
       ---------------------------------------------------------
       *****************************************************
   DIR Return to: Bugs
       *****************************************************
       #Post#: 25518--------------------------------------------------
       Opentype Features for Open Sans Regular doesn't working
       By: Lisa Yani Date: February 17, 2023, 9:12 am
       ---------------------------------------------------------
       I just discovered a bug when I started to self hosting a two
       fonts, winch is Open Sans and Source Sans Pro. Open Sans will
       display on the small text class and middle text class, and
       Source Sans Pro will display for body, Means that I replaced
       some body and smalltext fonts winch is formerly IBM Plex Sans
       fonts. When I add a OpenType feature at here below...
       [code]
       .smalltext, .middletext {
       font-family: 'Open Sans', 'Segoe UI', 'Roboto', 'Arial',
       sans-serif;
       font-feature-settings: "ss03";
       }
       [/code]
       ...then Open Sans fonts should changes the letter "I" and "J",
       but when I looked at homepage, I notice that Open Sans Regular
       has non-functioning OpenType Features even I used the latest
       version of Open Sans, I looked a Open Sans Bold and OpenType
       features are just worked fine. I am confused with this bug,
       could anyone help this?
       The demonstration of Open Sans Regular and Bold :
       Open Sans Regular:
       [attach=1]
       Open Sans Bold:
       [attach=2]
       #Post#: 25520--------------------------------------------------
       Re: Opentype Features for Open Sans Regular doesn't working
       By: CreateAForum Date: February 17, 2023, 12:18 pm
       ---------------------------------------------------------
       I am not really the best at CSS you probably know more than
       me....
       It might be a caching issue/clearing cache.
       *****************************************************