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

Fix regression of code links being blue (Cherry-pick of #336) #337

Merged
merged 1 commit into from
May 18, 2023

Conversation

Eric-Arellano
Copy link
Collaborator

Closes #335.

I git bisected this to
#292. Before, we weren't actually fully running theme.js because JavaScript errors prevented the file from fully executing. @coruscating identified that before the regression, the HTML elements did not have the class .has-code, but after they did. I suspect theme.js is responsible for that (but I couldn't figure out how!)

Either way, these rules about .has-code are bad. We should not be setting links to be blue.

Closes Qiskit#335.

I git bisected this to
Qiskit#292. Before, we
weren't actually fully running `theme.js` because JavaScript errors
prevented the file from fully executing. @coruscating identified that
before the regression, the HTML elements did not have the class
`.has-code`, but after they did. I suspect `theme.js` is responsible for
that (but I couldn't figure out how!)

Either way, these rules about `.has-code` are bad. We should not be
setting links to be blue.
@HuangJunye HuangJunye merged commit 43610d5 into Qiskit:1.12 May 18, 2023
2 checks passed
@Eric-Arellano Eric-Arellano deleted the cp-blue-links branch May 18, 2023 14:38
Eric-Arellano added a commit that referenced this pull request May 22, 2023
Tested on Experiments and Terra. Only known issue was fixed already:
#337.
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 this pull request may close these issues.

None yet

2 participants