marcb wrote:Personally, I do not think that there are real life situations where you really want nested cseignore tags. It makes little sense. So, what I had in mind was more the type of control that is done for the p tag in XHTML, where you have to close the tag and where you cannot open the next one before closing the previous one.
marcb wrote:I wasn’t aware that this already had been implemented, but I must admit that I never read the release notes. However, this does not yet seem to function as expected. I tested with a page that contained 2 cseignore blocks. You can find this page at http://www.xpragma.com/view199.php.
I first removed the closing tag of the first block, which should trigger the condition of nested cseignores. However, the validation only resulted in a closing error for a p tag, but no specific cseignore message.
marcb wrote:Side note: while doing these tests, I got a (correct) warning message 135 for an invalid character; which apparently currently seems to be missed by the batch validator.
marcb wrote:Yes, the URL I mentioned in my previous message is the one that contains an invalid character on line 135.
Users browsing this forum: Google [Bot] and 1 guest