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
{{ message }}
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
If I use Privly inside Github and use a coding reference, it doesn't show.
For eg:
If I type <title>Privly · <i class="fa fa-github"></i> Open Source</title>
Privly renders it without ``
@smcgregor details the following problem:
The screen capture below shows the HTML for the injected content above. It is wrapping the code in the code block, but since the injected iframe does not inherit the stylesheets of GitHub it does not display code blocks the same as GitHub.
I would say this is more something that could look better than an actual bug. The current design choice was made because we want the injected content to be as seamless with the surrounding content as possible. GitHub is only one site the content is displayed within, so saying it should change means you are saying that there is a way for it to look better on all websites-- not just GitHub.
This can even be extended to emails. Right now every field requires to input info in Privly. It should be one application to send all data. Data indifference could be applied here I guess, since all email apps require to:, subject:., body:.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I use Privly inside Github and use a coding reference, it doesn't show.
For eg:
If I type
<title>Privly · <i class="fa fa-github"></i> Open Source</title>
Privly renders it without ``
@smcgregor details the following problem:
The screen capture below shows the HTML for the injected content above. It is wrapping the code in the code block, but since the injected iframe does not inherit the stylesheets of GitHub it does not display code blocks the same as GitHub.
Stylesheet needs to be updated.
The text was updated successfully, but these errors were encountered: