![segoe ui font family download segoe ui font family download](http://pic.onlinewebfonts.com/screenshots/bbb24e6cd852b9ec144f5847705fe9fb.jpg)
Results in Chrome using the Times New Roman *Bold* face (note that there is no *Black* face of TNR).ĭoes NOT use Times New Roman Bold, it falls back to the 'sans-serif' generic. > to get Roboto Black across both platforms, something likeĬhrome's workaround has an interesting side-effect, in that it results in spurious "fake" font-family names being recognized: The default font, Times New Roman is used instead. Whether or not a change will be implemented, this situation should be clearly explained in the MDN font and font-family articles (and maybe font-weight and font-stretch as well). > misunderstanding the font family model(s). > beyond recognizing that it exists and that it's really a case of authors > I just don't think anyone has been focusing on the issue for the time being, But there's not been any clear decision as to exactly > some discussion of possibly adding hacks to deal with some of the common > I guess the bugs haven't simply been closed as INVALID because there's been Details (In reply to Jonathan Kew (:jfkthame) from comment #10) To get the Black face under GDI (I assume - have not tested) and to get Roboto Black across both platforms, something like GDI doesn't recognize Roboto Black as belonging to the Roboto family, and so font-weight can't find it. Will give you Roboto Bold rather than Black? If so, that's expected - it's simply the same issue, in reverse. Does anyone happen to know if oneĭo you mean that under GDI rendering, something like
![segoe ui font family download segoe ui font family download](https://www.cufonfonts.com/images/thumb/38688/segoe-ui-this-741x415-adb98e2604.jpg)
> The wrong font face is applied, like Roboto Bold instead of Roboto Black. > Sans ExtraLight, Ubuntu Medium and various Roboto font faces. When hardware acceleration is disabled, Firefox doesn't recognize DejaVu If we do add a font-family-compatibility hack of some kind, we can probably resolve these reports as duplicates. I just don't think anyone has been focusing on the issue for the time being, beyond recognizing that it exists and that it's really a case of authors misunderstanding the font family model(s). If and when we decide on a resolution, it should apply to them all. Yes, we have several reports that are really the same underlying issue. > would be useful to group the various reports together. > actually going to be handled on a per-font basis, in which case a meta bug > between condensed/stretched fonts and light/bold ones. > same problem? It seems like if there was a distinction to make, it would be Why are both bug 584769 and bug 644385 New? Don't they describe the exact But there's not been any clear decision as to exactly what (if anything) to do. I guess the bugs haven't simply been closed as INVALID because there's been some discussion of possibly adding hacks to deal with some of the common author confusion here. Is this recognized as a valid issue or not?Īs explained (here, by Boris and John, as well as elsewhere) this is not really a bug, it is behaving as designed, given that we're dealing with two different font platforms - GDI and DirectWrite - that present different font family structures. This report is still unconfirmed, while identical ones about other fonts > I hope someone can clear up a few things. The above approach works for me and is also the approach used by Open Sans and Google fonts.(In reply to Gingerbread Man from comment #9) (4) and (5) would be the same: font-face The problem is that I cannot do it work with Segoe UI Bold (I think the name is wrong). I have declared all the styles with in order to use the font-weight property to change the thickness of the font (it's a really cool feature!). I want to use the "Segoe UI" font in a website if it is installed in the user's computer.