| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/fvsz0mwtj |
Sorry, something went wrong.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 9668613:
|
Sorry, something went wrong.
|
Unfortunately, normalize does not support IE. Microsoft is also about to discontinue support for IE 11, do we still need to be IE compatible? cc @docsifyjs/reviewers |
Sorry, something went wrong.
|
@sy-records -- Given the near-universal support of normalize in other browsers, I think we can just mention the need for a ponyfill polyfill to support IE11 and provide a URL (below): We should verify that this ponyfill polyfill does in fact work, and specify that it needs to be included before any docsify-related <script> elements. |
Sorry, something went wrong.
|
I don't have IE11 to testing 😥 If we use this, do we want all users who need to search to add this polyfill? |
Sorry, something went wrong.
|
I can test in IE11 once the PR is ready. As for the ponyfill polyfill, it should be optional. Docsify should feature check for normalize support and use it if available. If not, then the search plugin should function as it always has. The docs should suggest the ponyfill polyfill only for those concerned with diacritical marks and IE11 support. This way it's a non- breaking enhancement. |
Sorry, something went wrong.
There was a problem hiding this comment.
Apologies for the slow response on this, @sy-records.
Verified working in modern browsers. Also verified working with and without polyfill in IE11. Great!
I did notice a few issues:
Search results are not displayed with their original diacritical marks. Notice in the screenshot below that the page contains the string "Let's go to café today". A search for "cafe" (no diacritical marks) matches "café" as it should, but the search result displayed under the search field shows the normalized version ("cafe") instead of the original text ("café").
Notice in the screenshot below that searching for "let" displays the matching search result text as "...Let's go to a cafe t...", but searching for "cafe" displays "...#39;s go to a cafe t...". That "#39;" looks like an incorrectly rendered HTML entity, but I haven't looked at the code to verify.
It looks like apostrophes break the search result highlighting.
FYI: Docsify is currently broken in IE11 due to issues with marked and the carbon ads plugin. I've already submitted fixes for marked (markedjs/marked#1877) and will address carbon ads soon. My tests in IE11 were done with a patched version of marked.
Sorry, something went wrong.
|
@jhildenbiddle Thanks for the test. The third one is solved. The second is an escapeHtml, I don t know how to deal with it for the time being. Solve by removed. The first question, I need to think about how to modify... 😂 That's it for now. If the original characters are used, the searched characters will not be selected, later we look at how to optimise the search plugin. |
Sorry, something went wrong.
There was a problem hiding this comment.
one small suggestion.
Otherwise great stuff.
THanks @sy-records
Sorry, something went wrong.
| }; | ||
| await docsifyInit(docsifyInitConfig); | ||
| await page.fill('input[type=search]', 'documentacion'); | ||
| await expect(page).toEqualText('.results-panel h2', 'Que es'); |
There was a problem hiding this comment.
is it possible to show the accent in the result ?
sorry if I missed any previous discussion regarding this. LMK
Sorry, something went wrong.
There was a problem hiding this comment.
I don't have a good idea how to do it...
Sorry, something went wrong.
There was a problem hiding this comment.
Looks like @sy-records got 2 of the 3 I listed. Perhaps we should open a new issue regarding missing diacritical marks in the search results so we can merge and release this PR.
Sorry, something went wrong.
There was a problem hiding this comment.
done. #1491
Sorry, something went wrong.
There was a problem hiding this comment.
Created a new issue for missing diacritical remarks in search results (#1492).
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
search ignore diacritical marks
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
resolve #1405
You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.