Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<code data-opaque bs-autolink-syntax=' #62

Closed
will-moore opened this issue Sep 27, 2021 · 2 comments · Fixed by #72
Closed

<code data-opaque bs-autolink-syntax=' #62

will-moore opened this issue Sep 27, 2021 · 2 comments · Fixed by #72

Comments

@will-moore
Copy link
Member

In https://ngff.openmicroscopy.org/latest/#image-layout I see a bunch of:

<code data-opaque bs-autolink-syntax='

which seem to be caused by ` in the docstring e.g. at

├── .zattrs # All labels will be listed in `.zattrs` e.g. `{ "labels": [ "original/0" ] }`

@glyg
Copy link
Contributor

glyg commented Nov 3, 2021

I tried substituting the triple backticks by <pre> tags and it does remove the <code opaque clutter but also removes the backticks in the comments:

http://api.csswg.org/bikeshed/?url=https://github.com/glyg/ngff/raw/back-tick/latest/index.bs

Maybe it's better to use <pre> ... </pre> as it's more robust anyway?

glyg added a commit to glyg/ngff that referenced this issue Nov 3, 2021
@will-moore
Copy link
Member Author

I see the <code> elements are still there in the HTML, so the backticks are still having an effect, it's just that the styling of those elements is no different from the surrounding text.
But 👍 for the "bug fix".

joshmoore added a commit that referenced this issue Nov 4, 2021
github-actions bot added a commit that referenced this issue Nov 4, 2021
Back tick - fixes #62

SHA: b5a1f6c
Reason: push, by @joshmoore

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants