Repository navigation
Handling of "<" in html #5679
Description
#5657 allows "<" in text nodes so that <p>{{ a < b ? c : d }}</p> does not throw.
However this is not valid html - < would have to be < to have a valid html.
One potential issue with the current approach is that in <p>{{ a <b && c > d }}</p> <b && c > would be parsed as an html tag and would not be easy for user to debug.
We could solve this by making the lexer aware of angular expression.
/cc @tbosch
edit {{ "<b>text</b>" }} could also cause pb
Activity
vicb commentedon Dec 8, 2015
/ref #5550 (comment)
DzmitryShylovich commentedon Dec 11, 2016
@vicb is this still an issue? Can't reproduce https://plnkr.co/edit/zJ2QPw7sTHw5wcl4Nc3h?p=preview
vicb commentedon Feb 8, 2017
Yep it is still an issue and should not be closed
DzmitryShylovich commentedon Feb 8, 2017
@vicb repro?
https://plnkr.co/edit/znDOr9YaVPJ8JRkXZxAN?p=preview doesn't throw
vicb commentedon Feb 9, 2017
Some failing forms are listed in the original report.
splincode commentedon Jul 26, 2018
@vicb Is the issue relevant?
9 remaining items
AndrewKushnir commentedon Jun 22, 2021
Discussed offline, PR #42605 does not resolve this issue, so I'm reopening this ticket.
alxhub commentedon Jun 30, 2021
Converting this to a bug, as this is fundamentally a problem with Angular's two-stage template parsing.
Yogu commentedon Aug 29, 2023
I guess with #48535 (Self-closing component tags) merged, and especially with built-in control flow coming, this probably no longer considered to be a bug? (Angular templates no longer being HTML in general)oops sorry for the noise, I misunderstood this issue. The issue is not that an HTML parser would not be able to parse an Angular template, but that Angular itself cannot parse it.
Here is a StackBlitz with a reproduction of the issue