Yes, if you want to link to the place where the HTML element appears then it’s actually easier than waht I was doing! I decided to link to the palce where the component is called becuase my app was using components defined in a complex use macro froma nother package, so the line numbers were kinda useless (they would point to a line in an “empty module” that only contained the use macro).
If the Source Inspector can provide a context menu with several source locations (using JS, probably), then we could expose a “stack trace” and the user could choose where to go: to the HTML element, to the component call, or even to the livevew mount() callback. The tricky thing would be how to generate the stack trace at the right level of abstraction. We probably don«t want a real stack trace, and instead we want a “simplified” stack trace that exposes the component hierarchy and maybe the controller function or the liveview mount() callback.
I would be interested in this, but I’m not sure how much time I’d have to work on it. The HTML engine seems complex (although the changes we’d require would probably be very simple once one understands the engine).
