We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've noticed that the cursor does not automatically blink in the most basic of demos (unless CSS is manually added to ensure the cursor blinks).
However, the full demo page works because there is a fadeOut example on the page.
fadeOut
Basic demo, broken, no fadeOut example included Working, after I've added a fadeOut example
Expected behavior: [What you expect to happen] Cursor should blink in basic demo.
Actual behavior: [What actually happens] Cursor does not blink.
Reproduces how often: [What percentage of the time does it reproduce?] 100%
My guess is that the bug is related to #285 and possible resolved by #306 (I have not tried)
The text was updated successfully, but these errors were encountered:
+1 Will this be fixed soon ?
Sorry, something went wrong.
Temporary solution:
CSS:
@keyframes typedjsBlink { 50% { opacity: 0; } } .typed-cursor { animation: typedjsBlink 0.7s infinite; }
18071ad
In line 552 of typed.js: this.cursor.className = 'typed-cursor';
Change for: this.cursor.className = 'typed-cursor typed-cursor--blink';
No branches or pull requests
Description
I've noticed that the cursor does not automatically blink in the most basic of demos (unless CSS is manually added to ensure the cursor blinks).
However, the full demo page works because there is a
fadeOut
example on the page.Demo
Basic demo, broken, no
fadeOut
example includedWorking, after I've added a
fadeOut
exampleExpected behavior: [What you expect to happen]
Cursor should blink in basic demo.
Actual behavior: [What actually happens]
Cursor does not blink.
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Additional Information
My guess is that the bug is related to #285 and possible resolved by #306 (I have not tried)
The text was updated successfully, but these errors were encountered: