Lightbox, back button, and vetoable closing

Context: https://github.com/ampproject/amp-react-prototype/pull/8/files#diff-c554b9bd31408e663cff269f69a1c567R51

Issues:

1. Some component libraries take a stand that “back button” support has to be arranged by the caller outside the lightbox (controlled). But that causes numerous issues, including inability to make closing vetoable.
2. Back button support is HARD. Standard doesn’t exist.

Supporting back button involves the following considerations:

• Rollback of history pop for vetoable close is especially hard and requires in-depth knowledge of the stack to re-push the popped states. Some routers (e.g. ReactRouter) allow history-stack blocking for this. But it’s rare and usually buggy.
• A naive history.pushState can break a React router and can never be fully featured.

See also #43 on the discussion about controlled-vs-uncontrolled lightbox API.

Commencez par les modifications de la lightbox référencées dans PR #8 et lisez la discussion dans issue #43. Étudiez comment l’historique du navigateur, les fermetures pouvant faire l’objet d’un veto et les interactions avec React Router affectent l’API contrôlée ou non contrôlée proposée. Le travail est terminé lorsqu’une approche décidée et documentée du comportement du bouton Retour et des fermetures pouvant faire l’objet d’un veto est définie.