Closed cosmicproc closed 8 months ago
Also, if desired, ,
That makes sense, although we don't currently use any on grapheneos.org but we use some on attestation.app.
Can you please submit this for https://github.com/GrapheneOS/AttestationServer too? We try to keep them mostly in sync, although the attestation site is a bit behind in some areas.
Sure
Not clear why GitHub is formatting that whole reply as a quote.
> Also, if desired, <input>, <select>, and <textarea> elements, which have the same behavior, can be added to the CSS rule as well.
That makes sense, although we don't currently use any on grapheneos.org but we use some on attestation.app.
Can you please submit this for https://github.com/GrapheneOS/AttestationServer too? We try to keep them mostly in sync, although the attestation site is a bit behind in some areas.
@cosmicproc Can you make this consistent with the attestation.app one even though we don't use these elements yet? It will be forgotten when we do use them otherwise.
Form elements don't inherit fonts by default. This causes
<button>
elements to have a browser-chosen font unlike the<a>
element that looks like a button in the home page. Also, if desired,<input>
,<select>
, and<textarea>
elements, which have the same behavior, can be added to the CSS rule as well.Home page button (actually an
Buttons in the web installer page (https://grapheneos.org/install/web)
These are actually different fonts
![image4](https://github.com/GrapheneOS/grapheneos.org/assets/126974221/5eae3cec-f9bd-4cc5-8596-7676a76c93aa)
<a>
element) (https://grapheneos.org/)Reference: https://stackoverflow.com/questions/26140050/why-is-font-family-not-inherited-in-button-tags-automatically