Open ulisesmac opened 10 months ago
@ulisesmac is that because 0x
is not using a x
but rather a ×
multiplication sign?
i.e 0xffff
vs 0×ffff
Is that the issue or is it something else?
@ulisesmac is that because
0x
is not using ax
but rather a×
multiplication sign?i.e
0xffff
vs0×ffff
Is that the issue or is it something else?
This is the link to figma: https://www.figma.com/file/WQZcp6S0EnzxdTL4taoKDv/Design-System-for-Mobile?type=design&node-id=1658-30911&mode=dev
It is an x
(letter), not ×
(sign)
Also, our text is not as bold as in designs, and I think we cannot change the weight since it is already being used to set the monospace style.
We also need Semibold and Medium variants to our Monospace fonts, and add them in quo2.foundations.typography namespace (plus integrate new variants in our components)
Bug Report
Problem
The monospace text is not reproducible by using our monospace style for the text component.
An example is the context-tag component, in figma we have:![image](https://github.com/status-im/status-mobile/assets/90291778/9d7c5457-cff6-4594-9486-3c54f21058f9)
which would be translated in our code to:
but it looks as follows:![image](https://github.com/status-im/status-mobile/assets/90291778/83fe91aa-21c2-4478-806c-59ca5fd5b64d)
Expected behavior
Looks the same as designs.
Reproduction
Navigate to the context-tag component in Quo2.preview:
type
asaddress
.