If the connection drops for less than 5-10 seconds (this happens even on my Cable Internet sometimes), it's no problem. Most timeouts and TCP connections are okay with complete dropouts for 30 or 60 seconds (sometimes longer), as long as your local LAN doesn't drop your network connection.

Doesn't that depend on the nature of the "drop"? When it's just lack of signal then sure, but when I see connections break even momentarily (on cable...), there's often some sort of feedback (I think sometimes it's a connection reset?) that causes the browser to just error immediately, and then I have to reload the page... despite still being on the same network with the same IPs and such.

That is because of the way your connection is being dropped/what your router is doing. It’s sending reset messages back to your client telling it your connection is dead, instead of trying to resend your packets - which then succeed when the connection is back up.

That's a possibility in theory; I haven't root-caused this to know what's happening in every case (again: not every drop is the same). Regardless, I'm just talking about what the average end-user might see; I don't really care where the blame goes.