New issue
Advanced search Search tips

Issue 873730 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Task



Sign in to add a comment

Stop exposing __gCrWeb.frameMessaging.registerFrame API.

Project Member Reported by michaeldo@chromium.org, Aug 13

Issue description

This API currently needs to be exposed because the frameId is generated at Document Start, but the frame cannot message the native application about it's existance until Document End time.

Once windowID is replaced with frameID, frame registration code should either:
- All be moved to Document End time (f.e. in setup_frame.js)
  or
- Move registration to run all at Document Start (frame_messaging.js), but queue the resulting 'FrameBecameAvailable' message until Document End time.
 
Components: Mobile>iOSWeb
Components: -Mobile>WebView>Glue
Components: -Mobile>iOSWeb Mobile>iOSWeb>ScriptInjections

Sign in to add a comment