User tests: Successful: Unsuccessful:
Pull Request for Issue #7927
Currently HTML parser of the com_finder INDEXER is adding spaces after
the endings of all HTML tags so that words at edges of BLOCK Tags are spaced properly
but this destroys words partly enclosed via inline HTML tags!
e.g. with input:
<h1>Title</h1><p>Paragraph</p>
<strong>M</strong>obile
Title Paragraph ....... which is correct (block tags)
M oblie ....... which is broken, (inline tags)
This PR adds the space at the begining of the tags,
thus avoiding a costly / more costly regular expression to add it at the end !
Not all regular expressions are "performance evil", they can be very fast by e.g.
-- Starting with fixed texts, and also using OR on fixed texts
-- Also the performance of a regular expression can depend a lot on the input
None
Maybe add some more unit tests ? to have some test for inline tags too ?
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_finder |
Labels |
Added:
?
|
I have tested this item
Before test Mobile not found
After test Mobile found
I have tested this item
I have tested this item
@brianteeman can you please retest?
no need to retest as the only change was in a comment
Status | Pending | ⇒ | Ready to Commit |
Status "Ready To Commit".
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-07-22 20:55:37 |
Closed_By | ⇒ | HLeithner | |
Labels |
Added:
?
|
thx
Please tell me if i have gotten the list of desired tags correctly