Broken Handling of Certain Hash Characters from elFinder Connector #2802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the elFinder docs, it has the below content:
This doesn't actually hold as characters such as ".", ":" are valid HTML ID characters, but when used in a JQuery hash selector, elFinder would behave strangely as internally, it does it in such a way where these characters are confused with CSS/JQuery selector characters instead of being part of the HTML ID.
For more information on the above issue, refer to the accepted answer on this stackoverflow post.
As such, I've made a pull request in an attempt to solve the above issue. So essentially, instead of:
It now uses:
Benchmark
I ran a small benchmark to see any performance difference, and it turns out using $(document.getElementById("")) is actually faster.
I copied the code within this text file and ran it on the elfinder demo page.
Benchmark.txt
Benchmark Results