True, but that ambiguity seems unavoidable regardless of the solution, because you always have the possibility of one link being a child of another. Even if you allowed linking on the directly on the tr element, people could still put anchors inside it.
I would suggest the behaviour should apply if, and only if, there was only a single visible anchor descendant. If you included more than one anchor, the property would be ignored and the browser behaviour the same as it is now.
Another benefit of making it a CSS property would be that you could use media queries to turn it off and on. This kind of linking is especially common, and useful, on mobile, where regular hyperlinks can be difficult to click on, especially if they’re data-bound and potentially small (e.g. a table of titles or usernames, which could be “a”, “b”, etc.).