Start with the experience
A design file describes an intended experience, but it cannot answer every question about a working product. What happens while data loads? What if a name is unusually long? What does a keyboard user encounter first? These are design decisions as much as implementation decisions.
Make constraints visible
When designers and developers review the same prototype, technical constraints become useful information. A content model may need to change. An animation might need a simpler mobile version. Resolving these questions early protects the idea and makes the work easier to maintain.
Review the working thing
The browser is where the experience becomes real. Review the actual interface together, with real content, at different sizes and with a keyboard. Treat those reviews as part of design rather than a final inspection after it.