Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.8k
Fix the end condition for the embed content handling loop#1824
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
vercelbot commentedJun 22, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The latest updates on your projects. Learn more aboutVercel for Git ↗︎
|
codesandbox-cibot commentedJun 22, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
This pull request is automatically built and testable inCodeSandbox. To see build info of the built libraries, clickhere or the icon next to each commit SHA. Latest deployment of this branch, based on commit73dc6d6:
|
The fix has been sent upstream indocsifyjs/docsify#1824
The fix has been sent upstream indocsifyjs/docsify#1824
The fix has been sent upstream indocsifyjs/docsify#1824
The fix has been sent upstream indocsifyjs/docsify#1824
@sy-records@Koooooo-7 gently ping for this simple patch :-) |
up! thanks for your consideration |
3bfb1cd to95f5c45Compare
Fixes#1822
Summary
This changes (and effectively fixes) the end condition for the embeds handling loop.
What kind of change does this PR introduce?
Bugfix
For any code change,
I didn't see any test related to embed but I'd be happy to update some if needed.
I especially looked at the "embed" page in the documentation, and everything looked good in my opinion.
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
Related issue, if any:
#1822
Tested in the following browsers: