Glad that you found it helpful. 👏

Semantically, you should use div when nothing else makes sense.
If you just want to group few elements together and it doesn't make sense to use section, header, footer, main, aside, article, nav, etc then go for div.
Never ever add a text inside a div and use click handler to behave like a button. A div is a container of another item and it should do that only.

Agree, use target=_blank only where needed.
I would consider "jump to the top of the page" as navigation as we are actually navigating the user to the top of the page. Just make sure you take care of "open in new tab" functionality.
A lot of user does right-click and click something from the menu like copy this link or open in new window/tab. That should not break the functionality.

A clickable item can either navigate the user or do some action. If the behavior is not among these or contains both, we probably need to check the UX if it's correct.

Personally, I take the thumb rule of "if it looks like link, make it behave as link"

Rest should behave as button.

And when making a button, there are multiple ways to do it.

There are various kind of users and one natural instinct for a user is that if it looks like link, they might try to open in new tab. But that is also vary small percentage of users. Normally the non-tech users will browse in a natural flow where app can guide them in a natural flow.

I personally am a heavy user of open in new tab and I have 4-5 windows with at-least 20 tabs in each. I hate my habit of doing this but yeah it happens.

UX is very tricky thing around this and there is no blanket statement to cover this kind of experience. Every use-case is different and need to be handled with specific Usability Testings

Pankaj Patel Makes sense

I used to do that too 😅. Thanks for reading. Hope it was helpful.

Thanks for reading 🤝