-
Notifications
You must be signed in to change notification settings - Fork 130
ApplicationConfig unescaped #116
Comments
@mamont77 are you running the latest version? Escaping should be applied there... |
@Ocramius, yes. I'am using latest master. |
Could you please paste the HTML generated by the toolbar? I didn't find the location where the output would not be correctly escaped.. |
Sorry, I could not attach a file, unsupported format. |
@mamont77 if I get this correctly, it's a problem in The problems are at https://github.com/mamont77/fcontrol/blob/master/temp.html#L367, right? If so, then this issue should be opened against |
@Ocramius I'm not convinced by your analysis.
Based on the configuration dumped, I'd argue it's a problem with |
@weierophinney no analysis: I just stopped after finding out that it's not ZDT ;) |
Odd -- I took the relevant parts of the configuration:
and wrote a test to see if the values were being escaped. They were. In fact, all quotes, all angle brackets, and a number of other characters were being escaped for HTML. This makes me wonder if it's either (a) browser-specific, or (b) an issue with how the JS library is handling the data. |
This repository has been closed and moved to laminas/laminas-developer-tools; a new issue has been opened at laminas/laminas-developer-tools#20. |
Hi.
Broken page because the code is displayed unescaped.
It seems there is a problem in ConfigCollector::unserializeArray().
The text was updated successfully, but these errors were encountered: