Sigh. For every step forward, there's a step backwards.
That's not true. The output of the plugin is ALWAYS take to be aXML. If it was any other way, aXML would look like the following (when outputting HTML):
plugin produces aXML or HTML code, if the plugin returned aXML, the parser takes that aXML code and produces HTML code, browser takes that HTML code and produces text. if the plugin returned HTML, browser takes that HTML code and produces text.
There is no such check, because such a check is impossible. So, again, what actually happens is
plugin produces (what is taken to be) aXML code, parser takes that aXML code and produces HTML code, browser takes that HTML code and produces text.
Plugins that don't produce aXML are buggy.
In reply to Re^10: Thanks to Ikegami, Chromatic & Corion
by ikegami
in thread Thanks to Ikegami, Chromatic & Corion
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |