#504@patch: Fixes XmlParser error parse with tags.

[Mas0nShi]

now we have perfected tag matching again...

Fixes #504

[capricorn86]

I think we need to find a solution where we turn off the parser when a <script> start tag has been found until a </script> end tag comes.

[Mas0nShi]

I think we need to find a solution where we turn off the parser when a <script> start tag has been found until a </script> end tag comes.

I find the MARKUP_REGEXP maybe wrong? so i added exclusion < beacuse we can't input < and > when we declare tag..

[capricorn86]

Yes, this fixes this specific problem, but we still have problems in these kind of scenarios (where <div> is parsed as a start element):

<script>
   for(let i = 0; i < 10;i++) {
	    console.log('<div>');
   }
</script>

[Mas0nShi]

Yes, this fixes this specific problem, but we still have problems in these kind of scenarios (where <div> is parsed as a start element):

<script>
   for(let i = 0; i < 10;i++) {
	    console.log('<div>');
   }
</script>

what? I am good running when i tested this.

[Mas0nShi]

Yes, this fixes this specific problem, but we still have problems in these kind of scenarios (where <div> is parsed as a start element):

<script>
   for(let i = 0; i < 10;i++) {
	    console.log('<div>');
   }
</script>

Maybe the problem you're talking about is #376 solves?
we had declare ChildLessElements to stop parse the next-level tags.

[capricorn86]

Yes, this fixes this specific problem, but we still have problems in these kind of scenarios (where <div> is parsed as a start element):

<script>
   for(let i = 0; i < 10;i++) {
	    console.log('<div>');
   }
</script>

Maybe the problem you're talking about is #376 solves? we had declare ChildLessElements to stop parse the next-level tags.

Yes, maybe you are right! I will make a test as well, just to be sure 🙂

[capricorn86]

It seems to work great! Good job! ⭐