Proposed investigation: add new Canvas API text-related attributes #50
Replies: 1 comment
-
Results of initial investigationfontKerning For SC, this would only impact for Phrase entitys which have set their Conclusion: will not fix. Adding this new functionality to SC will require considerable work for little additional benefit - SC is not a text engine! fontStretch While SC is (potentially) capable of displaying variable fonts if they have been properly loaded/configured elsewhere, it is beyond the scope of the library to manipulate those fonts when displaying them on the canvas (again: SC is not a text engine). To update SC to include such functionality will require considerable work - in particular when it comes to measuring the width and position of each glyph - work required to support individual glyph styling and/or positioning along a path. Conclusion: will not fix. Instead, it makes sense to remove all mention of fontVariant from the existing code base to simplify the Phrase entity. fontVariantCaps SC already supports the Conclusion: will not fix. In addition it makes sense to deprecate existing functionality around font variants given that there's no guarantee browsers will continue to support the existing |
Beta Was this translation helpful? Give feedback.
-
Issue
The CanvasRenderingContext2D API has some (relatively) new properties:
These properties normally live in the CSS font string. We need to do work to incorporate them into SC in a way that they can be picked up from the font string as well as being individually set in the normal SC way.
Beta Was this translation helpful? Give feedback.
All reactions