Same key fields in different sections rendered incorrectly

[AliceLeyou]

What happened?

When using multiple fields with the same key within a table, they are all rendered with the value of the first occurence of the key.
Source view:

Reading view:

A similar thing happens when using fields with the same keys in different sections. Once I use an already used key in a different section, it is rendered with the corresponding occurence of the key in the first section.
Source view:

Reading view:

I believe this has to do with PR-2098, where the replacing of inline fields was adjusted to correctly display LaTeX notation. I believe this is due to MarkdownPostProcessorContext.getSectionInfo having unexpected return values. MarkdownSectionInformation.text seems to contain the text of the entire document instead of just the current section. For tables MarkdownSectionInformation.lineStart and MarkdownSectionInformation.lineEnd seem to include all rows of the table, so splicing the text according to those values also doesn't seem to solve the issue.
The only solution that I found while looking through this is to check whether the value of the inline field can be interpreted as HTML. That fixes both the original issue as well as this one, but I doubt it's the best solution for this (also the first time I looked into Dataview code, so I have no clue if it breaks something somewhere else).

const isHTMLString = (str: string) => {
    const document = new DOMParser().parseFromString(str, "text/html");
    return Array.from(document.body.childNodes).some((node: ChildNode) => node.nodeType === 1);
};
if (inlineFieldsFromText &&
    inlineFieldsFromText[index].key == inlineFields[index].key &&
    isHTMLString(inlineFields[index].value)
    ) { ... }

DQL

No response

JS

No response

Dataview Version

0.5.64

Obsidian Version

1.5.3

OS

Windows