No worries! I'm on Windows 10 and was using Brave (a chrome variant).
If I were to hazard a guess at what might have caused the bug, my first instinct would be that you're probably doing some kind of raycast/collision box check when the player hits the interact button to see if he's trying to interact with the door, and it's probably colliding with something else. As a result, I wouldn't be surprised if when you try to get a pointer/reference to the door object, you might end up trying to call a function that doesn't exist, or if you cast the collided object, you could be left with a null reference if it's not actually a door. I could be wrong of course, but that would be the first thing I checked if I were you. :)