iOS Context Menu iFrame Support Finch Experiment |
||||||||||
Issue descriptionTechnical feature description: Supporting the Context Menu in iFrames on iOS requires sending element details back to the app using JavaScript's |postMessage|. (Instead of directly returning DOM element details from a JavaScript function.) Eng owner: michaeldo Design doc (send to chrome-design-docs@): https://docs.google.com/document/d/1gfVy-A5ebNfG9wG_rise34HsDpyZoWi1Cn4oV6hhTKU/edit?hl=en# Metrics: ContextMenu.DOMElementFetchDuration - This metric will monitor the time it takes to return element details for the Context Menu. Since the new implementation will change the way element details are fetched from the DOM for the main frame, we will monitor to ensure the performance impact is acceptable. (If performance issues are discovered, we can explore using the old implementation if the DOM element is found in the main frame.)
,
Mar 28 2018
,
Mar 28 2018
What percentage is this intended for launch on Stable of 67? I thought this was just Stable-Exp of 1-5%?
,
Mar 28 2018
I just spoke with Eugene and we can start with 1-5 rollout. If metrics look good in M67, we should ramp up to 100%. There is no need for an independent experiment in M67. (That was a potential option in M66, but the feature is now complete so it makes sense to enable it if the metrics look good during the roll out.)
,
Mar 28 2018
Thanks for the clarification!
,
Mar 29 2018
Since there's already another launch bug for context menu in iframes (817517), I'm marking this ticket about experimental rollout as a non-rollout bug that's blocking the original one.
,
Mar 30 2018
This experiment has been enabled on Canary and Dev with the name "IOSContextMenuFindElementAtPoint".
,
Mar 30 2018
Add NextAction date to review preliminary metrics and request Beta experiment approval if they look good.
,
Apr 5 2018
,
Apr 9 2018
The NextAction date has arrived: 2018-04-09
,
Apr 26 2018
Updated https://bugs.chromium.org/p/chromium/issues/detail?id=817517
,
Apr 26 2018
,
Apr 26 2018
,
May 15 2018
Removing Launch-Status since we'll be deprecating this field and the approval is already captured in blocked bug.
,
May 16 2018
This task is now obsolete since the launch is being tracked in crbug.com/817517. Marking as such since it is listed as blocking the launch. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by gov...@chromium.org
, Mar 28 2018