String#escapeHTML checks, String#unescapeHTML cleanup
Reported by Mark Caudill | August 8th, 2009 @ 12:05 AM
JDD's rewrite of String#escapeHTML uses a textNode.data = str; result = node.innerHTML; concept to extract an escaped version of the string. Does the length of the string determine if this is faster than the old style of using the .replace functionality?
Also, String#unescapeHTML could use a bit of documentation since it's pretty complex. Maybe a bit of formatting.
Comments and changes to this ticket
-
John-David Dalton August 8th, 2009 @ 02:23 AM
Really looking at the benchmarks of small string as I have done work with big strings and they seem fine.
Will update the unit tests to show the big string benchmarks. -
John-David Dalton February 13th, 2010 @ 02:37 AM
The
replacereally limited the usefulness of this method, though I am not against another method that keeps that simple functionality, I knowPHPhas something similar. -
John-David Dalton April 15th, 2010 @ 02:41 AM
- State changed from “new” to “resolved”
I believe the methods in question have been cleaned up a few times now :D
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
JavaScript frameworks share similar features and functionality such as DOM manipulation, event registration, and CSS selector engines. FuseJS attempts to incorporate the strengths of these frameworks into one stable, efficient, and optimized core JavaScript framework.
John-David Dalton
Mark Caudill