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

Issue resolved, theme problem on time-complexity-analyzer page #18 #57

Merged
merged 2 commits into from
Oct 4, 2024

Conversation

Hustler004
Copy link
Contributor

I tweaked the implementation of theme-related buttons, used toggle functionality, changed function name so that they sound more intuitive, also the issue was solved by changing "window.onload = initializeComplexityChart();" command in analyzer.js file to "document.addEventListener("DOMContentLoaded", function () {
// Your analyser.js logic goes here
initializeComplexityChart();
});"

Let me know if the issue still resides!

Copy link

netlify bot commented Oct 4, 2024

Deploy Preview for codeittool ready!

Name Link
🔨 Latest commit bdc884e
🔍 Latest deploy log https://app.netlify.com/sites/codeittool/deploys/6700038b4de777000803fefb
😎 Deploy Preview https://deploy-preview-57--codeittool.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@Hustler004 Hustler004 changed the title #18 - Issue resolved, theme problem on time-complexity-analyzer page Issue resolved, theme problem on time-complexity-analyzer page #18 Oct 4, 2024
@multiverseweb
Copy link
Owner

@Hustler004 looks good to me. But I think the color of the chart is not changing to black in light mode. As the issue of code refiner theme button is fixed in this PR, I'm merging it.

@multiverseweb multiverseweb merged commit 1138214 into multiverseweb:main Oct 4, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants