You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 6, 2026. It is now read-only.
ReadNumericEntityNode function handles the readings different way than ReadNamedEntityNode. Numeric entity is read as TEXT_NODE and named entities are read as ENTITY_REFERENCE_NODE, also different events are triggered which causes HTMLParser to handle them in separate ways, which may cause problems when parsing HTML. I.e. /</; and /&/#60/; are handled in separate ways.
You guys know if this is intended functionality or not? Does HTML parsing spec state that these has to be parsed on different ways or something?
HTMLp/HtmlReader.pas
Line 497 in 4883f99
ReadNumericEntityNode function handles the readings different way than ReadNamedEntityNode. Numeric entity is read as TEXT_NODE and named entities are read as ENTITY_REFERENCE_NODE, also different events are triggered which causes HTMLParser to handle them in separate ways, which may cause problems when parsing HTML. I.e. /</; and /&/#60/; are handled in separate ways.
You guys know if this is intended functionality or not? Does HTML parsing spec state that these has to be parsed on different ways or something?
I can also provide PR for fixing this if needed.