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
@tomkralidis@wxtim Apologies for not visiting here for many years!
I think styles are important. The original intent was to support both the monochrome and the bi-colour version of the symbols, as specificed by WMO and ICAO.
The context has changed slightly, in that SVG2.0 has clarified its relationship with surrounding web pages and CSS, etc., so there may be a requirement to inherit styles from the context. However, as the orginal design was to support viewing in low level light, or red light, and on low resolution devices, many acessibility have already been addressed.
Also, black and red are still the only readily available, non-poisonous, archival inks, thus addressing another requirement.
The only reason for not implementing the bi-colour and monochrome options was uncertainty on the best approach and what the market supported.
Looks like we have defaults of:
stroke:#000000
fill:#000000
Add a utility which allows the user to specify a hex, rgb, or color to update an SVG.
The text was updated successfully, but these errors were encountered: