Hi BJ
The start/end properties are provided in the parse tree by some, but not all, parse tree rules. Thus they can actually be seen in the parse tree preview; see the illustration below.
The reason that the start/end properties are not set by all parse tree rules is an unfinished refactoring of the parser mechanism. Initially, I had used an approach where each parse tree rule did almost all of its work with a single regexp that both matched the parse rule and returned the parameters needed. It ended up not being adequate for the demands of the HTML element/widget, and so I started using a more conventional approach using regexps for speculative matching, and manual parsing for the rest. You can see the approach here:
A by-product of that coding style is the start/end properties in the parse tree. Clearly, there’s a lot of UX things that would require consistent availability of these properties, and I’d be open to revising the remaining parsers to give us that behaviour.
Best wishes
Jeremy