Relaxed CR exit criteria to match known implementation plans

[tidoust]

See related discussion in: #406

---

Preview | Diff

[markafoltz]

LGTM

[anssiko]

@schien, does this work for you, considering Mozilla's implementation plans?

[schien]

Sorry for the late response.
Due to the engineering resource availability constraint, no resource to work on upgrading API changes after December 2016 on the first half of 2017. 1-UA implementation will stay in Firefox Nightly/Aurora for now. The old 2-UAs implementation for Firefox and Firefox OS is deprecated and no plan for new 2-UAs implementation.

The exit criteria might not work for Mozilla if it requires the browser to implement both 1-UA and 2-UA mode.

[tidoust]

Thanks @schien,

The new exit criteria would not require browsers to implement both 1-UA and 2-UA mode, so that should work for you.

That said, there have been a couple of updates since December 2016 that would require updates to the 1-UA implementation in Firefox Nightly/Aurora for the spec to transition to Proposed Recommendation:

• sandboxing flags moved to the PresentationRequest construction.
• restriction to secure contexts (exit criteria allude to the possibility for that not to be ready provided there exists a plan to do so)

[anssiko]

@schien, as @tidoust outlined above, the updated exit criteria in this PR should work better for you.

[schien]

understood, lgtm.