You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running some cross-browser tests on the KineticJS display, I found that the default font display on Mac browsers went to what looks like Times New Roman. This isn't really what I wanted; WIndows browsers just used the font which I specified for the tag. To get the proper font display, I had to manually set the font for each text node. I'm not sure if this is a bug, and if it is, a bug for which platform.
That said, quick solution for this that I'd propose would be to use cascaded font styles, and let me set the font on a higher-level element and have lower-level elements default to that unless otherwise declared.
The text was updated successfully, but these errors were encountered:
This is an interesting idea, although I'm not sure it would fit cleanly into the KineticJS node tree model. I.e., it might be odd to set text properties on a stage or layer node.
Maybe it would work better if it weren't so much setting explicit properties as just default values for them to inherit? Alternatively, making the default font pull from whatever the containing tag uses would improve cross-platform consistency.
Running some cross-browser tests on the KineticJS display, I found that the default font display on Mac browsers went to what looks like Times New Roman. This isn't really what I wanted; WIndows browsers just used the font which I specified for the tag. To get the proper font display, I had to manually set the font for each text node. I'm not sure if this is a bug, and if it is, a bug for which platform.
That said, quick solution for this that I'd propose would be to use cascaded font styles, and let me set the font on a higher-level element and have lower-level elements default to that unless otherwise declared.
The text was updated successfully, but these errors were encountered: